LeoDiep commented on issue #19944:
URL: https://github.com/apache/superset/issues/19944#issuecomment-1594009441

   > facing the same problem while import from v1.5.0 to v2.1.0. Also there is 
a notice appear everytime accessing to the imported dashboard: Error loading 
chart datasources. Filters may not work correctly. Although I have changed the 
scope as it is as the old dashboard and it work just fine as the old one. This 
notice confuse users and annoyin.
   
   I have to go to every chart and click Save again to make the notification 
dissapear.
   
   
   
   
   > Facing the same issue with **_Cross Filter scoping_**. Steps to reproduce:
   > 
   > 1. Create a dashboard with more than one or two chart. _(My dashboard was 
with 3 tabs and 6 charts.)_
   > 2. enable cross filter
   > 3. Restrict cross-filtering for any chart to none. That is, Apply to 
specific panels -> deselect all panels
   > 4. Export the dashboard
   > 5. Delete the dashboard and their corresponding charts
   > 6. Import dashboard
   >    **Actual result:**
   >    Cross filter scoping will remain `Apply to all panels` for all charts.
   > 
   > **Expected result:** Import should preserve the cross filter scoping for a 
chart.
   > 
   > **Observation**: Importing the dashboard seems to assign the new chart 
ids. Check the properties of a dashboard (edit dashboard -> edit properties -> 
advance JSON metadata)
   > 
   > 
   > The chart ids 1, 2, 3, 4, 5, 6 were the old chart ids when I exported the 
dashboard first time. It has correct cross-filter scoping. Deleting a dashboard 
and corresponding charts, importing the dashboard generates new chart ids (from 
37 to 42) and assigns `apply to all panels` cross filter scoping to all charts. 
If you export the dashboard again, you can able to see the new chart ids in the 
dashboard's yaml file.
   
   I guess this was because the Superset launching by docker already have chart 
ids from 1 to 36 as example charts


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to