Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
By any chance could you confirm if you using any tool to get this information, if so, could you try with a different tool to see if the result is consistent?
Could you indicate what privileges you have ?
Could you try to use the following Security Rule and configure it for the user you are using to get the results of QRS API (https://community.qlik.com/t5/Knowledge/Guidance-on-how-to-conclude-if-the-issue-is-Security-Rule/ta...)
If none of the above works, could you try to add an additional header Context: ManagementAccess to see if that makes a difference (https://help.qlik.com/en-US/sense-developer/August2021/Subsystems/RepositoryServiceAPI/Content/Sense...)?
If nothing works, it will be necessary to follow up with a case, attach a backup of the repository DB and indicate the userid you are using to make the QRS API Calls.
Hope it helps!
By any chance could you confirm if you using any tool to get this information, if so, could you try with a different tool to see if the result is consistent?
Could you indicate what privileges you have ?
Could you try to use the following Security Rule and configure it for the user you are using to get the results of QRS API (https://community.qlik.com/t5/Knowledge/Guidance-on-how-to-conclude-if-the-issue-is-Security-Rule/ta...)
If none of the above works, could you try to add an additional header Context: ManagementAccess to see if that makes a difference (https://help.qlik.com/en-US/sense-developer/August2021/Subsystems/RepositoryServiceAPI/Content/Sense...)?
If nothing works, it will be necessary to follow up with a case, attach a backup of the repository DB and indicate the userid you are using to make the QRS API Calls.
Hope it helps!
Hi Nadia,
Thanks for your help. We discovered since that the issue was with a script used to format the data. It was cutting off lower nodes on the tree.
Thank you for letting us know @AndyBurnsJPM