03-21-2013 08:26 AM
In DI Studio job, When I delete a stage in the process flow, then the mappings defined in the previous stages are broken.
Example :: Source(s) -> Stage B -> Stage C -> Stage D -> Stage E -> Target table
If I delete/drop stage E and replace it with some other stage, then the mappings of C,D get broken.....
Is there any way/logic/trick by which I can drop a stage in the process flow and have the mappings intact in the other stages...
Thanks for any help!
03-21-2013 08:38 AM
Sounds strange. What version are you using?
Can you give examples of which transformations this happens?
In you example, removing E (Table Loader or equivalent), mappings between C and D should be intact.
What exactly is happening, do you lose the target columns of D, or just the mappings (1-1, expressions) between C and D?
03-22-2013 05:15 AM
LinusH , You are right.. I tried again and the mapping is still there... Not sure , first time how mappings disappeared....
Also another thing, in Process Designer, we have tabs -> Process Editor and Source Editor
After doing some changes in Process Editor , when Source Editor is selected... the code gets generated automatically in the source editor....
suppose if I want make changes directly(add one or two lines of code logic) in Source Editor, will that be possible... or source editor only displays code as per process editor?
Thanks for your help!
03-22-2013 07:23 AM
It is possible, but absolutely NOT best practice. As soon as you edit the source code, everything in the metadata that you have defined will have no effect on the code.
So, if you want add some code, do it in pre/post code to the job/transformations.
If you want to change the, that's a different story, and needs separate discussions on each occasion I believe... Do you have any special changes in mind?