Hi,
I have been going through the same thing. When I copy visualizations from one dashto another, I end up with multiple modules.
What I have done to solve this is look for the ID of the second module in the dashboard in the specification (hit CTRL + q + /) and modify it to keep the first ID. It's something like:
"dataSources": {
"version": "1.0",
"sources": [
{
"id": "model0000018868bc89c5_00000002",
"assetId": "i67302C38B8E44B70A2C66EE1C1395526",
"type": "module",
"name": "Module Name Here",
"shaping": {
"references": {},
"embeddedModuleUpToDate": true
}
}
]
},
------------------------------
JEAM COELHO
Cognos Solution Architect
LinkedIn:
https://www.linkedin.com/in/jeamcoelho/------------------------------
Original Message:
Sent: Mon October 23, 2023 06:26 AM
From: Marc Reed
Subject: Dashboard Embedded Data Modules - how do you remove them?
Some dashboard actions will cause a dashboard to create an embedded data module. For example, create a calculation in a dashboard and you end up with an embedded data module.
Whilst there is no harm in embedded data modules, they do confuse our users, such as :
- why do I have 3 datasources to the same Data Module?
(caused by users copying/pasting visualisations between dashboards) - When i create a new visualisation, which of these 3 data sources should I use, are they all the same?
- When a new calculation is added to the source data module, if it has the same Id as the a calculation in the embedded data module, which takes precedence.
Whilst a user shouldn't care if a data module is embedded or not - it does cause confusion.
Is there an easy way to remove a dashboard's embedded data module? I have tried relinking but they are persistent.
------------------------------
Marc Reed
------------------------------