You need to sign in to do that
Don't have an account?
Alok Agrawal
How to deploy WaveDataFlow along with referenced Data Model and Permission Set in a single deployment
Reaching out to Einstein Analytics experts who have experience working with WaveDataFlow metadata type. https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_wavedataflow.htm (https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_wavedataflow.htm" style="color:#0563c1; text-decoration:underline)
I am trying to deploy this metadata along with the data model that the dataflow references and the permission set for the data model in a single deployment. However, I am encountering a tricky behavior where Salesforce expects the data model to be accessible to the Wave integration user at the time of deployment. Currently, I am working around this problem by deploying the data model and permission set in 1st deployment, assigning the permission set to the Wave integration user, and then doing a second deployment for WaveDataFlow.
Please let me know if you are aware of any deployment approach that allows all metadata to be deployed in a single push. For me single deployment is important as I need to deploy this using a second generation unlocked package and breaking the codebase into 2 packages due to this limitation is not an elegant solution. Appreciate your help!
I am trying to deploy this metadata along with the data model that the dataflow references and the permission set for the data model in a single deployment. However, I am encountering a tricky behavior where Salesforce expects the data model to be accessible to the Wave integration user at the time of deployment. Currently, I am working around this problem by deploying the data model and permission set in 1st deployment, assigning the permission set to the Wave integration user, and then doing a second deployment for WaveDataFlow.
Please let me know if you are aware of any deployment approach that allows all metadata to be deployed in a single push. For me single deployment is important as I need to deploy this using a second generation unlocked package and breaking the codebase into 2 packages due to this limitation is not an elegant solution. Appreciate your help!
Anudeep (Salesforce Developers)
As far as I know, you can deploy the permission set but the user assignment to the permission is not reflected. See this post