I facing an error after exporting dashboards into the new version of superset installed in my docker like as
follows
There is no chart definition associated with this component, could it have been deleted? Delete this container and save to remove this message.
when i open charts manually and saved again then only this error will gone. i have almost 40 dashboards with 100+ charts, how could we resolve this issue
Related
I'm using Visual Studio (SSDT) to modeling and deploy my model to PowerBI Premium Workspace and create my report in PowerBI desktop, however now I've added new tables and applied changes on that and I'm not able to deploy it again.
Tabular Model Designer
Exception has been thrown by the target of an invocation
Cannot deploy metadata. Reason: Failed to save modifications to the server. Error returned: 'Failed to commit the metadata change, please try again later.
Technical Details:
RootActivityId: 7c302aa2-e8d3-417f-8fb7-3bdc9969e14f
After the last Microsoft update this issue was resolved. Now the model deploy using XMLA endpoint is working well again. Tks
I have uploaded a report to PBI Cloud with several bookmarks and different data models like tables and different charts. Now I made some changes to this report and published it by replacing the existing one. Some charts were deleted and some new were newly added. When navigating directly to the report in PBI cloud I can see the changes. But the changes are not applied for the App which is connected with that report.
Is there any further step needed to perform so that the models in the PBI Cloud "App" get also updated?
In the workspace there is an Update app button, that you need to click,
This will take you through the process of republishing the app
Is it possible to share a dashboard chart and keep its configuration?
Whenever I try it the resulting iFrame just shows the default configuration for that metric. Aggregations, type of chart, etc, are gone.
I could only find URL parameters to enable auto refresh (isAutoRefresh) and changing the timeframe.
You can share a chart of a custom dashboard by following these instructions.
If you have already followed the instructions provided and it is not working as expected, I would then suggest to file a PIT here. You can file a PIT if you have encountered unexpected behavior with one of GCP's products or to request for a new feature to be implemented within GCP.
I have one Tabular SSAS project & I have deployed it on SQL Server Analysis Service 2012.
Then I have created a BISM connection to that deployed project as in following way.
Then I have created one PowerPivot excel report out of that BISM workbook using its connection string & it is working correctly in Excel.
But when I upload it to the SharePoint, it give me following error while refreshing the Data from BISM workbook.
this error is observed only when I open it on browser i.e. Excel Web Access.
but the same error is not observed when I refresh the report in Microsoft Excel 2013.
why is it giving error on only SharePoint i.e. Excel Services. due to this I am not able to change Slicer's either.
One of the solution I found was to use some Hot Fix of SQL Server. but I haven't tried this. Plz refer the below link Hot Fix for SQl Service Pack 1 Update
Please help!
Thanks in advance.
This refresh should be possible, assuming permissions are set up correctly. You should post ULS logs for the time period of the refresh.
Does this same thing happen if you do a scheduled refresh (and choose refresh now)?
I am trying to export a MySQL database from a Amazon Web Service Relation Database Service. I have tried connecting and exporting through MySQL Workbench and tried through command line in the EC2 server. But the tables exports still end up incomplete.
One table exports the first 5459 rows (1.1Mb) and then stops half way through the row.
another table exports the first 676 rows (7.7Mb) and then stops half way through the row again, this table should have about 39000 rows.
I haven't used Amazon Wen Services before or Linux or MySQL, I normally work on Windows servers with Microsoft SQL. Has anyone had this error before or know what the cause could be?