help with understanding more about XLM as it relates to Report Templates.
I am posting to this group because the Customers concern is performance and not impacting it.
I am working with a Client who wants to eliminate all unnecessary metadata, in the form of dependencies possible on their
ESM 6.5.1 system. It's not my place to argue or debate with a Customer's wishes.
Their desire is to NOT import packages from an ESM of the same build, and I am working to get this one exemption.
I can say that there *should* be no issues with unnecessary dependencies, but I would like to be able to say this with great
confidence, and I am not an XML expert.
I did change the name of the Report Templates bundle that I exported to .zip instead of .arb and used GNU zip with the -d
(decompress) option to get to the XML code. I don't see any overhead. Presumably the only dependencies would be to the
Reports that use these custom Templates.
Inside the XML code i can clearly see some expected, acceptable Dependencies, and where some custom company name
image files are being imported but I have no idea what is inside all the cruft gobleygook which looks more like rot-13 encryption than understandable data.
Has anyone done this exercise before? Are there any XML gurus out there who could look at an exported Report Template file
from your own ESM and see if there is any unnecessary overhead? Obviously I won't be posting the Customers Template file publicly.
I just want some help in being able to say with great assurance there is no unnecessary overhead in this kind of Resource.
Of course it does seem intuitive that there is not an issue.
Thanks, David Hawley