Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
MDouglas1687874333
Contributor III
Contributor III

Unable to write to XML twice in same subjob

Hi,

I am having an issue where I am unable to write to an XML file twice in a single subjob.

Image of subjob:
talend flow.png

Above is the subjob, the Fixed flow simply outputs a table with four rows with 2 columns, the tmap then splits this into two more flows based on the value of a column. The output xmls both write to the same xml file and are set to append. What happens is only one of the flow rows is written to the file, always the lowest in the order (out2 flow in this case), and the first flow is not written. I am unsure if it is overwriting the file or not, but both the outputs write to different sections, shown below:
out1.pngout2.png

Is this simply due to how the subjob is structured under the hood or is there some extra step I need to add between the tmap and outputxmls? 

Labels (6)
1 Solution

Accepted Solutions
Dave_Simo
Creator II
Creator II

Hello @MDouglas1687874333 

I don't know if you have managed to resolve your XML construction problem but what works is a design like below, broken down into 2 parts with an OnComponentOk and adding an append on the second tAdvancedFileOutputXML.

Dave_Simo_0-1756392752024.png

Dave_Simo_1-1756392785589.png

Best Regards

View solution in original post

2 Replies
Dave_Simo
Creator II
Creator II

Hello @MDouglas1687874333 

I don't know if you have managed to resolve your XML construction problem but what works is a design like below, broken down into 2 parts with an OnComponentOk and adding an append on the second tAdvancedFileOutputXML.

Dave_Simo_0-1756392752024.png

Dave_Simo_1-1756392785589.png

Best Regards

MDouglas1687874333
Contributor III
Contributor III
Author

Thanks and yeah, this is basically what the final solution became, which seems like a lot of extra steps but I guess is simply due to how the system is structured.