Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I would like to retrieve Master Items (Dimensions and Measures) used on a Server in Apps.
I have tried MasterConfig , GINQ0 Master Item Manager and the Governed Metrics Service (GMS). All have their limitations. GINQ CSV export cannot deal with newlines in definitions, the GMS is complex and unsupported, MasterConfig cannot load Master Items from existing Dashboards.
What currently works is extracting Master Items from Apps using the QRS Websocket JSON interface via Python and then uploading via MasterConfig into new Apps. I would prefer a solution that works completely from the front end.
I would prefer a solution that works completely from the front end. Therefore I tried to create an App connecting using a REST connector to the QRS REST API using "https://localhost/qrs/app/object/full"
This can load measure descriptions, name, etc. But measure definitions are missing and the field “attributes” seems to be an encoded string. How can I retrieve measure definition and all the other attributes of a measure or Master Item using the QRS REST API?
Nothing inside of an app is exposed via the QRS API, so @Øystein_Kolsrud 's pointer to the Engine API is going to be the route that you will need to go. The QRS API, when it comes to apps, has some high level meta-data like lists of sheets, lists of master items, etc. But the actual content of those assets inside of an app are not exposed via the QRS API.
I think you need to go through the engine API to get that type of information. In particular you want these endpoints:
https://help.qlik.com/en-US/sense-developer/June2019/APIs/EngineAPI/services-Doc-GetDimension.html
https://help.qlik.com/en-US/sense-developer/June2019/APIs/EngineAPI/services-Doc-GetMeasure.html
And then get the properties of those.
Hi, I thanks for your reply, but I am looking for a solution using the QRS REST API.
Nothing inside of an app is exposed via the QRS API, so @Øystein_Kolsrud 's pointer to the Engine API is going to be the route that you will need to go. The QRS API, when it comes to apps, has some high level meta-data like lists of sheets, lists of master items, etc. But the actual content of those assets inside of an app are not exposed via the QRS API.
Hi,
Getting this information from the REST API is not possible, but you could use the corectl tool, published as open source by Qlik:
https://github.com/qlik-oss/corectl
Under the hood this tool uses the engine API though.