You’re offline. This is a read only version of the page.
Hi,
We have made an object which is pretty much a list of checkboxes that the enduser can click wether it's on or off. The end customer is allowed to modify the labels of the fields as they see fit to suit their business needs.
We've made a report on top of this where they get a list per customer and all the fields he/she has ticked in his object. The report reads the following views : EntityView, AttributeView and LocalizedLabelLogicalView to read the "customized" labels from the database so that we don't have to redo the report for every single customer.
As I came to realize later a regular user can only read the Filtered.....-named views. So to have this work we have to grant SELECT access on the views above. Is there a different way to do this that is supported "out-of-the-box"? Is granting SELECT priviligies on these views even supported/a good idea.
*This post is locked for comments
I have the same question (0)
I suggest that you create one view that collects the data from the other views you need and then use the created view in your report. This method would require you to only grant SELECT privileges to a single view in the database and would address the concern of Microsoft overwriting your changes when applying a RollUp. Just remember to test your view out after applying update to verify MS has not changed the functionality of one of the referenced views.
Share
Report
All responses (
Answers (
4
