Hi experts,
I've an unusual problem that seems to making me lose my sanity. I've a custom table (doesn't extend another table) and it doesn't seem to be appearing in the dropdown when trying to create a new report.
This user already has report_admin and report_user roles. The ACLs defined on the table are as follows:
Read:
The affected user does not have the above role, so I understand that he won't be able to view records/data in the table, but that shouldn't prevent it from selecting in the reporting screen, right?
Interestingly, I created a dummy user in dev environment and added only "report_admin" role to him and he was able to select the table in the reports screen. The ACLs on the table are same in dev and prod environment.
After searching on this topic, there were suggestions to create a "report_on" ACL on the table but in our dev environment, it's not there and still the table was available to be selected from the dropdown for the dummy user. So it's unlikely that that is causing the issue.
The affected user in Prod does have many other roles so I'm wondering if any of those roles is superseding the report_admin role and preventing listing of the table in the "Create Report" screen? Is there a way to find out which role is conflicting if that is the case?
@Ankur Bawiskar- sorry for the tag but wouldn't hurt to consult with the expert.
Hello @Nisar2
Please check this thread below.
It could be a read ACL on the table that is restricting the access.
Also, can you please check if the reporting is allowed from the list view of the custom table.
- Go to the list view
- Right click on the list header to open the context menu.
- Do you see the 2 reporting options highlighted here?
