Resolve column naming issue with XML Source Transform in Sagent

Product Feature: Design Studio

 

Issue

The user selects the elements he want in XML Source, but the transform generates multiple columns with the same name. This is very inconvenient. Why does not XML source use the parent element's name as prefix, like it does when checking "flatten". 
              
User-added image

Cause

Using "Rename Columns" seem to mess up the columns when anything changes in the workflow.

Resolution

UPDATED: November 21, 2017
The behavior is seen with the sample xsd file. This behavior is as per design and if the user has any specific requirement then it might be treated as enhancement request after product management consideration. Raise it in Ideal Portal with the use-case.

Workaround:
When elements in XML Source modified and/or selection changed, remove 'Rename Column' transform and again add it in the plan.