thank you, qwerty - a colleague of mine is fluent in scripting EA, will ask him.
@Oliver, PTC Source Integrity has an unresolved issue:
https://www.ptcusercommunity.com/thread/40277and PTC refuses to change that in a timely manner.
I know of two tools that have problems with that one: EA and VectorCAST.
In general all tools using the XML specification to the extend having lines longer than 16k characters without a new-line.
With source files PTC reads lines, not characters, and cannot accept lines longer than 16k.
EA exports xml files as configurable items for version control. Sometimes they come with lines longer than 16k. I have seen ~150k, but that model is far from ready. I expect even longer lines.
One work-around would be to check-in the xml files as binaries into PTC. This has a bad influence on size and performance of the PTC database for very big files. Exporting an EA package could grow too big.
The other solution that I am taking is, to break long lines by inserting newline characters at places where not only XML but also EA accepts them. A good place is at sub-strings "},{" after the comma. I am inserting as few as possible.
In one post above I am detailing the steps to be taken manually when checking such packages into PTC.
Now I am going to automate this in order to hide this inconvenience from users in other teams.
Best Regards
Rolf