[ ] Regression (a behavior that used to work and stopped working in a new release)
[x ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead go to https://varigence.com/Forums?forumName=Biml or email support@varigence.com
[ ] Other... Please describe:
Current behavior
When importing a valid DTSX package that has an aliased column name, the resulting biml omits the alias property and simply uses the source column name, which can be problematic and is not the intended behavior.
Minimal reproduction of the problem with instructions
Convert the attached file to a dtsx file and pass it through the importer.
I'm submitting a...
Current behavior
When importing a valid DTSX package that has an aliased column name, the resulting biml omits the alias property and simply uses the source column name, which can be problematic and is not the intended behavior.
Minimal reproduction of the problem with instructions
Convert the attached file to a dtsx file and pass it through the importer.
MergeJoinTestDtsx.txt
What is the motivation / use case for changing the behavior?
Replicating SSIS behavior in biml
Environment