We recently learned the hard way that objects created via Data Designer are not supported with Data Permissions. To us, this means one of a few things impact-wise:
- Either we cannot control the visibility of records in a Data Designer table.
- We have to create a custom reporting layer, by mirroring DD tables into a Low Volume table, automate the population of data to the reporting layer, update all of our reports and dashboards to report off these new tables, and then apply data permissions accordingly.
- Scrap the use of Data Designer altogether, and do it the old-fashioned way of creating our own custom tables and populating them with data from the rules engine.
- Create multiple versions of each Data Designer table, each report, and each dashboard, and show them to the appropriate users.
In my opinion, the most scalable option here is to completely abandon the use of the Data Designer feature, and go back to a time when Data Designer didn’t exist. Which is truly an unfortunate outcome.
We would love to see Data Designer enhanced to allow for Data Permissions to be applied, and filter records accordingly.