Hi Helene
Thanks so much for the feedback. We have an OEM solution where we have a stream per client and a standard app which is published to all clients. We have many fields available in the QVDs (data layer) that can get loaded, but what is important to one is not necessarily to another. My idea is to have the full possible data model in a main app (template/standard app) and then having the clients select which fields they want in their version of the published app. We are already doing this using Excel files, but this is obviously not scalable as we need to update all of the Excel files when adding a field. We are now moving this to an external application (rather than Excel files). I would ideally like to extract the QS template app's data model using the external application. I can then use this to populate the choices that we expose to the client dynamically, rather than having to update the choices manually.
I'll have a look at Catwalk to see what they do :).
Maybe someone else has an easy example that I can piggy back off.
Regards,
Mauritz
