If the data is not changing too often, I think I would create a macro, which stores the possible value sets and return them to the caller doors/windows with returned parameters. And if there is a need to change the stored data, I would regenerate the macro – maybe I would write a python script to create a macro in xml format from the data source, and then compile the macro with LP_XMLConverter. After that, you can change the macro in the project libraries.
This solution would be much faster in AC, than always reading xml files in paramscript. Of course, it needs some more work, when there are changes.
Team Leader, Library Team