Symptom
- Data Access Control (DAC) restriction won't be applied when linked dimensions are used, where e.g. live Datasphere and import model is linked in SAC.
- DAC is not implemented while filtering across the models.
- If the user is selecting the dimension from the live Datasphere model as data source to build a filter or a widget, the DAC restrictions won't be applied.
- If the user is selecting the dimension from the import model as data source to build a filter or a widget, the DAC restrictions will be applied.
- Warning on the linked dimensions: "Blending is currently not supported between linked models for Optimized Design mode. Currently only filtering across models is supported."
- ODE story.
- DAC is set on import model/public dimension.
- DAC is not set on Datasphere model.
Environment
- SAP Analytics Cloud
- SAP Datasphere
Reproducing the Issue
- Login to SAC.
- Create an import model with Data Access Control (DAC).
- Create e.g. an analytic model on Datasphere.
- Create a SAC story and link dimensions between the import model and the Datasphere model connected via live connection.
- If the user is selecting the dimension from the live Datasphere model as data source to build a filter or a widget, the DAC restrictions won't be applied.
- If the user is selecting the dimension from the import model as data source to build a filter or a widget, the DAC restrictions will be applied.
Or
- Insert a table/chart or a filter based on the dimension from the live Datasphere model as data source. => Not OK, all the values from Datasphere will be listed by default. Expectation is, that no values should be visible for the user, which has DAC restrictions.
- Create an input control created based on the dimension from the import model as data source. All members is selected by default. => OK, only the restricted values are listed.
- Now filter on one of the values.
- Check the table => OK, The values in the table will be refreshed, and from now no values will be listed, as expected.
Cause
- By design product behavior.
- Linking dimensions for filtering across models doesn't change how the available list of values for that dimension is fetched from either model. DAC is also completely "transparent" for the client, as it should be, so:
- Fetching data for the import data model will be restricted based on the DAC (done by the server which has access to the DAC definition) while fetching data for the DSP model will not be restricted by the DSP server since, it does not have the same DAC definition.
- Filtering on either model will apply the same filter on queries for data from the other model.
Resolution
- By design product behavior.
- Please, open an enhancement request for the topic per KBA 2424376 - How to create an enhancement request for SAP Analytics Cloud?
This document and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice.
This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
See Also
- 3167189 - Data Access Control (DAC) in SAP Analytics Cloud Collective KBA
- 2423166 - Users are able to see master data (dimension members) and enter transaction data when data access control is enabled in SAP Analytics Cloud
- 2569847 - Where can you find SAC user assistance (help) to use, configure, and operate it more effectively?
- Have a question? Ask it here and let our amazing SAP community help! Or reply and share your knowledge!
- 2487011 - What information do I need to provide when opening a case for SAP Analytics Cloud?
- 2511489 - Troubleshooting performance issues in SAP Analytics Cloud
- Search for SAP Analytics Cloud content using SAP for Me, Google or Bing:
- https://me.sap.com/servicessupport/search#?q=SAP%20Analytics%20Cloud%20OR%20SAC&tab=All
- https://www.google.com/search?q=site%3Ahttps%3A%2F%2Fuserapps.support.sap.com+SAP+Analytics+Cloud
- https://www.bing.com/search?q=site%3Ahttps%3A%2F%2Fuserapps.support.sap.com+SAP+Analytics+Cloud
- Note: Add relevant text or warning/error messages to the text search field to filter results.
- SAP Analytics Cloud Connection Guide
- Getting Started with SAP Analytics Cloud Expert Community page
- SAP Analytics Cloud Get More Help and SAP Support
- Need More Help? Contact Support or visit the solution finder today!
Your feedback is important to help us improve our knowledge base.
Keywords
SAP Cloud for Planning, sc4p, c4p, cforp, cloudforplanning, Cloud for Analytics, Cloud4Analytics, CloudforAnalytics, Cloud 4 Planning, BOC, SAPBusinessObjectsCloud, BusinessObjectsCloud, BOBJcloud, BOCloud., SAC, SAP AC, Cloud-Analytics, CloudAnalytics, SAPCloudAnalytics,Error, Issue, System, Data, User, Unable, Access, Connection, Sac, Connector, Live, Acquisition, Up, Set, setup, Model, BW, Connect, Story, Tenant, Import, Failed, Using, Working, SAML, SSO, sapanalyticscloud, sap analytical cloud, sap analytical cloud, SAC, sap analyst cloud, connected, failure, stopped, sap analyst cloud, https://hcs.cloud.sap, https://hanacloudservices.cloud.sap, https://cloudanalytics.accounts.ondemand.com, https://hanacloudservices-us.accounts.ondemand.com, https://www.sap.com, https://help.sap.com, predictive analytics (analysis), data analysis (analytics) tools, analytics tools, sap analytics cloud, data literacy, advanced analytics, data democratization, analytics software, real time analytics, self service analytics, advanced data analytics, analytics as a service, analytics cloud / cloud analytics, saas analytics, cloud bi, enterprise planning, cloud data analytics, cloud based analytics, analytics cloud platform, modern analytics, real time analysis, cloud analytics solution(s), what is sap analytics cloud, cloud analytics tools, analytics in the cloud, cloud analytics software epm, business intelligence, sap analyst cloud,sac hot news sac kba , KBA , LOD-ANA-DES-SMQ , SAP Analytics Cloud Story Metadata and Queries , Problem
SAP Knowledge Base Article - Public