SAS Data Integration Studio, DataFlux Data Management Studio, SAS/ACCESS, SAS Data Loader for Hadoop and others

DI studio has different mappings in Mapping tab as compared to Code tab

Accepted Solution Solved
Reply
Frequent Contributor
Posts: 82
Accepted Solution

DI studio has different mappings in Mapping tab as compared to Code tab

Some times in SAS Data Integration Studio, there will be a step (e.g a SQL JOIN) that will show some mappings when you click on 'Select' on the right hand navigation menu inside the step.

But then if you go to 'Code' tab, there will be code that overrides  those mappings with different mappings.

In this case, at execution time, will the program executed what is in hte 'Code' tab or what is on the 'Mapping' tab?


Accepted Solutions
Solution
‎06-13-2014 09:34 PM
Respected Advisor
Posts: 4,173

Re: DI studio has different mappings in Mapping tab as compared to Code tab

Posted in reply to eagles_dare13

DI Studio code generation is metadata driven so the code generated is based on what you define in metadata (so for example what you set up in the mapping tab). The code tab shows you then the generated code exactly how it will be used for executing the job.

But of course: The mapping definitions will only take effect as long as you don't switch over to "user written" (drop down box in the code tab right above the code pane). As soon as you're using "user written" instead of "auto generated" it's no more the metadata (eg. the mapping) which gets used to generate the code but what you're actually manually typing as "code" in the code tab.

The code used will always be what you see under the code tab.

It is best practice to use "auto generated" and have everything metadata driven as far as possible.

View solution in original post


All Replies
Solution
‎06-13-2014 09:34 PM
Respected Advisor
Posts: 4,173

Re: DI studio has different mappings in Mapping tab as compared to Code tab

Posted in reply to eagles_dare13

DI Studio code generation is metadata driven so the code generated is based on what you define in metadata (so for example what you set up in the mapping tab). The code tab shows you then the generated code exactly how it will be used for executing the job.

But of course: The mapping definitions will only take effect as long as you don't switch over to "user written" (drop down box in the code tab right above the code pane). As soon as you're using "user written" instead of "auto generated" it's no more the metadata (eg. the mapping) which gets used to generate the code but what you're actually manually typing as "code" in the code tab.

The code used will always be what you see under the code tab.

It is best practice to use "auto generated" and have everything metadata driven as far as possible.

🔒 This topic is solved and locked.

Need further help from the community? Please ask a new question.

Discussion stats
  • 1 reply
  • 264 views
  • 0 likes
  • 2 in conversation