Skip to main content
Solved

Api call returns Null Array, while others in the same permission group do work.

  • January 20, 2025
  • 2 replies
  • 35 views

Dennis1690
Vanguard
Forum|alt.badge.img+4

Hi wisers,

For Reporting purposes I’m trying to retrieve data from our Thinkwise Application to Power BI. I’ve set up SF roles, permissions and coupled the roles in IAM after deployment. Also I’ve checked the groups effective permissions on the bugged table (agreements) and confirmed that it has the corresponding permissions. 

However when sending a GET request for data it returns an empty array (example screenshot 1).

When sending a GET request to any other table in the same role/ permission group it does return data (screenshot 2)

Next to the basics of roles and permissions I do not know where to look/ solve this issue, any suggestions? Thanks in advance.
 

screenshot 1
screenshot 2

 

Best answer by Dick van den Brink

Hi Dennis,

Did you also validate the prefilter permissions? Maybe on some of the roles the “Always on” setting is enabled.

You can validate that from the “Roles” screen in the Software Factory.

Also, you can maybe try check the query in the `account/ui/dbEventLog` log page. Note, I believe the user needs development rights for this. After opening this page, you can execute the same GET request from your browser and you should see the query Indicium executed.

View original
This topic has been closed for comments

Forum|alt.badge.img+3

Hi Dennis,

Did you also validate the prefilter permissions? Maybe on some of the roles the “Always on” setting is enabled.

You can validate that from the “Roles” screen in the Software Factory.

Also, you can maybe try check the query in the `account/ui/dbEventLog` log page. Note, I believe the user needs development rights for this. After opening this page, you can execute the same GET request from your browser and you should see the query Indicium executed.


Dennis1690
Vanguard
Forum|alt.badge.img+4

Hi Dick,

Thank you for your response, it was indeed an always on prefilter that conflicted with the api call. 

Thank you for your help.

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings