We are taking steps to make our moderation process friendlier while ensuring that SAP Community continues to comply with the Digital Services Act (DSA). Learn more in this What’s New post.
Hello,Depending on your requirements and constraints, those would be the approaches that come to mind (from better to worse in terms of ease of implementation and probably performance):Use an account hierarchy defined in DSP. In case only additions a...
Hello, Correct command is: datasphere config cache init --host "<url>"Refer to the official help for command syntaxes: https://help.sap.com/docs/SAP_DATASPHERE/d0ecd6f297ac40249072a44df0549c1a/d483a0f480af452e9dda47f885ab87ad.html?locale=en-US.You ca...
Hello,This usually happens when a dimension/association/attribute has been unchecked and re-checked (added) at the analytic model level. After deployment, Datasphere will recreate a new internal ID for that dimension and it won't be recognized by the...
Hi,As far as I know there is currently no standard way to achieve this.We implemented a workaround for this using Data Access Controls.Each of our models have a calculated field with a hardcoded value representing the ID of the model. Then we secure ...
