Apex Code Development You need to sign in to do that
Don't have an account?
kumar_Al Manage package of einstein analytics assets give the issues with datasets connection
I created a simple analytics dashboard with two different lenses of the different dataset, I connect those datasets using https://help.salesforce.com/articleView?id=bi_dashboard_data_source_connections.htm&type=0 ,
it's working Properly.
If we create a managed package with all assets like analytics app, dataflow, dataset and dashboards it creates successfully, but if we deploy it on other org for testing purposes. it showing error while deploying.
Error :
1) (Dashboard_Name) No Dataset found for Developer Name: Dataset_Name
Dashboard_Name: No Dataset found for Developer Name: Dataset_Name
2)(Dashboard_Name) Wave Asset doesn't existing in the Org.
Dashboard_Name: Wave Asset doesn't existing in the Org.
But if we remove the given connection between dataset from all dashboard, and package it again it's getting install successfully.
but that dataset connection is necessary for my dashboards.
it's working Properly.
If we create a managed package with all assets like analytics app, dataflow, dataset and dashboards it creates successfully, but if we deploy it on other org for testing purposes. it showing error while deploying.
Error :
1) (Dashboard_Name) No Dataset found for Developer Name: Dataset_Name
Dashboard_Name: No Dataset found for Developer Name: Dataset_Name
2)(Dashboard_Name) Wave Asset doesn't existing in the Org.
Dashboard_Name: Wave Asset doesn't existing in the Org.
But if we remove the given connection between dataset from all dashboard, and package it again it's getting install successfully.
but that dataset connection is necessary for my dashboards.
The issue is caused by lacking namespace prefix in the dashboard's JSON file.
Once the namespace prefix is set all API names are changed to from 'Name' to 'Prefix__Name' but it doesn't work properly.
In the JSON file under 'dataSourceLinks' section, there is a "namespace" attribute set to "". This is causing the issue described above.
Solution: namespace prefix has to be manually added to the "namespace" attribute.
The same issue is related to images and SAQL steps.