Two problems:
- Datamodels store old connection information without the user being aware. That increases the chance of accidentally exposing credentials to a different security context. Sisense R&D said that the reason is to show Recent Sources.
- When you change a dataset, you can end up with two copies of the dataset, which is confusing.
Ideas for improvements (take some or all):
- Sisense could track the Recent Sources separately. Then Sisense could automatically remove empty datasets.
- Sisense could show empty datasets under Data Sources in the data model editor UI, and give the user a delete button for them.
- The Data Model editor could have a drag-and-drop to move tables between data sources.
- When you click export, there could be a checkbox "Remove data source connection information".
More detail about the problems here: https://community.sisense.com/t5/support-portal/bd-p/SupportPortal?page=casedetails&caseId=500Pk00000Es4PyIAJ and here:https://community.sisense.com/t5/help-and-how-to/models-have-empty-datasets/m-p/20632#M222
