Send a API from visualization / extension into Qrs
Hi
I am trying to send a API request into Qrs,
The purpose is to save the last click of the user about some topic like language, date format etc.
When user clicks on its preference, I want to save it into custom property (in the qrs?), and every running I will read it into var, and when the app is loaded the selection will present.
I am spend a lot of time with the documentation, foroms etc. any help will be appropriate.
Hey @MendyS , you cannot save this info into QRS. Based on your requirements, seems you need to first set and save language preferences, then apply them into a kind of default selections when Qlik app is opened, correct?
For saving part, if you want to stay with native funcionalities, bookmarks could be a good choice, but users have to select their bookmakrs manually.
Another option could be to create a custom extension which will read current selections on languages, and then store these info somewhere. Then Qlik app or extension it self can read these info during reload and apply selections on language prefernces.
what I want to do is enter the value into the Custom Property. i found the method - qlik.callRepository that allows us to put and get the values from the Custom Property. Today I saw the Qlik deprecated the method, so is there an option to connect to QRS API via JS in an extension?
You can connect to QRS from JS code, but Custom Properties are not intended to be used for your use case. Custom Properties work into QMC for assign custom values then implement Securoty Rules for providing access to Qlik resources. From our doc "You create a custom property to be able to use your own values in the security rules. You define one or more values for the custom property, and use these in the security rule for a resource".
Is this a JS connection from a front end app or a back end service? What is your authentication you would like to use and what is the current auth method set in virtual proxy?
From a JS point of view, using QRS is just a matter of making fetch calls to REST API endpoints. Biggest part is implementing authentication method.
