User Review( votes)
Recently I had written an article for Nigel Frank that list down step by step process of using XML Source Component of KingswaySoft for integration with Dynamics 365 CE
We have used XML Source Component to read the XML files.
The packages that we developed were running fine from Visual Studio SSDT but on deployment for one of our package that was using Script Component we were getting the below error while running from within SQL.
After a lot of debugging and spending a good amount of time to figure out the issue, we realized that the value of one of the input columns was not being passed to Script Component from XML Source component i.e. _ParentKeyField
This is a special column which XML Source Component adds for the child records through which we can associate it to the parent record.
This happens when we are running it from SQL and only for the Script Component. This worked fine while running it from within SSDT and in other packages even from SQL when we weren’t using Script Component.
As a quick fix, we applied XLST Transformation to put the same tag for the child records also and to refer that instead of _ParentKeyField
In parallel, we also asked the same question to the KingswaySoft Support team (firstname.lastname@example.org)
One thing I would like to explicitly mention is that KingswaySoft support team is one of the best out there, not only you will get the response immediately, but also their team is very knowledgeable.
Below is the response we got
As suggested after setting the RunInOptimizedMode property to False for the Data Flow components the issue got fixed.
This property indicates whether the Data Flow task runs in optimized mode (RunInOptimizedMode property). Optimized mode improves performance by removing unused columns, outputs, and components from the data flow.
Hope it helps..