Click HERE to see how Saviynt Intelligence is transforming the industry. |
08/29/2024 11:48 AM
Hi Team,
We have a requirement to display all the users from Organization for a logged in user where logged in user is a owner of that organization.
We have created the Runtime Analytics and assigned a Usergroup to it as a owner:
SELECT u.username as User_ID, u.firstname as FIRST_NAME, u.lastname as LAST_NAME, u.email as EMAIL, u.phonenumber as PHONENUMBER, u.enddate as ENDDATE, u.owner as MANAGER, c.customername as ORGANIZATION_ID, c.displayname as ORGANIZATION_NAME, u.street as ADDRESS, u.city as CITY, u.customproperty4 as POSTAL_CODE, u.customproperty5 as MOBILE_NUMBER, u.comments as USERCOMMENTS FROM users u JOIN customer_users cu on cu.userkey=u.userkey JOIN customer c on cu.customerkey=c.customerkey where c.customerkey IN (select customerkey from organization_owners where userkey=${user.id})
However after running the analytics from ADMIN view and checking if that shows the correct result based on logged in user, I'm getting the below error:
08/29/2024 11:51 AM
08/29/2024 11:54 AM
Hi @rushikeshvartak ,
The user have multiple customed SAV Role assigned to him however which feature you were talking about could you please let me know?
08/29/2024 12:20 PM
check in browser console which api is causing issue
08/30/2024 03:21 AM
Hi @rushikeshvartak
I'm getting the below error through browser console.
/ECM/analyticsHistoryES/undefined/api/idw/res/file?path=/app/usr/theme.json:1 Failed to load resource: the server responded with a status of 404 ()
I had attached the Feature Access and Webservices screenshot here. Could you please me with it.
08/30/2024 07:07 AM
Hello @rushikeshvartak
I have identified the feature access that was causing the error message: "access denied". The feature access that needed to be enabled was "Show Analytics Flat History". Once I added this feature access, I was able to view the analytics without any issues.
However, I noticed that the analytics reports were not displaying data based on the logged-in user. Instead, only the reports generated by users from the Admin console were appearing.
I would appreciate it if you could provide further guidance or assistance on how to resolve this issue.
08/30/2024 07:25 AM
Use USERCONEXT approch