Our developers worked in parallel to develop a dashboard by working independently on their own copies. They then pulled all the widgets together into one dashboard and now have multiple connections to the same data module. It isn't causing any problems now but there will likely be confusion in the long run when updating the data module and associated widgets. I think what happened is they worked on their own copies of the data module and then pinned widgets before relinking to the primary data module but have asked them to clarify exactly how they did it. I can't seem to be able to tell which widgets are tied to which connection from the ctrl-. properties since they are exactly the same. The only way I can think of to rectify this would be to relink the extra connections to a different module, let widgets break and fix them individually. I think then I would be able to remove the extraneous connections once they are no longer used. Is that really the only way to fix this?

------------------------------
Robert Hofstetter
------------------------------

#CognosAnalyticswithWatson

Hello Robert, 

have you tried to update a dashboard JSON specification directly? In Dashboard Edit mode you can get its specification using a key shortctut : CTRL + q + / . Then for each widget you can change modelRef id. Also in sources array I would delete all unnecessary relations to the data Modules in data sources - sources array. 

I tried it on very small dashboard and it worked. Maybe it could help you as well.

Regards,

Jiri. 

------------------------------
Jiri Smrz
------------------------------

Original Message:
Sent: Tue February 02, 2021 10:44 AM
From: Robert Hofstetter
Subject: Dashboard with multiple connections to the same data module

Our developers worked in parallel to develop a dashboard by working independently on their own copies. They then pulled all the widgets together into one dashboard and now have multiple connections to the same data module. It isn't causing any problems now but there will likely be confusion in the long run when updating the data module and associated widgets. I think what happened is they worked on their own copies of the data module and then pinned widgets before relinking to the primary data module but have asked them to clarify exactly how they did it. I can't seem to be able to tell which widgets are tied to which connection from the ctrl-. properties since they are exactly the same. The only way I can think of to rectify this would be to relink the extra connections to a different module, let widgets break and fix them individually. I think then I would be able to remove the extraneous connections once they are no longer used. Is that really the only way to fix this?

------------------------------
Robert Hofstetter
------------------------------

#CognosAnalyticswithWatson

Jiri,

Awesome. I couldn't remember the ctrl+q+/ combination to get the spec. That helped a lot. Thank you.

------------------------------
Robert Hofstetter
------------------------------

Original Message:
Sent: Wed February 03, 2021 10:10 AM
From: Jiri Smrz
Subject: Dashboard with multiple connections to the same data module

Hello Robert, 

have you tried to update a dashboard JSON specification directly? In Dashboard Edit mode you can get its specification using a key shortctut : CTRL + q + / . Then for each widget you can change modelRef id. Also in sources array I would delete all unnecessary relations to the data Modules in data sources - sources array. 

I tried it on very small dashboard and it worked. Maybe it could help you as well.

Regards,

Jiri. 

------------------------------
Jiri Smrz

Original Message:
Sent: Tue February 02, 2021 10:44 AM
From: Robert Hofstetter
Subject: Dashboard with multiple connections to the same data module

Our developers worked in parallel to develop a dashboard by working independently on their own copies. They then pulled all the widgets together into one dashboard and now have multiple connections to the same data module. It isn't causing any problems now but there will likely be confusion in the long run when updating the data module and associated widgets. I think what happened is they worked on their own copies of the data module and then pinned widgets before relinking to the primary data module but have asked them to clarify exactly how they did it. I can't seem to be able to tell which widgets are tied to which connection from the ctrl-. properties since they are exactly the same. The only way I can think of to rectify this would be to relink the extra connections to a different module, let widgets break and fix them individually. I think then I would be able to remove the extraneous connections once they are no longer used. Is that really the only way to fix this?

------------------------------
Robert Hofstetter
------------------------------

#CognosAnalyticswithWatson

Hi Robert, 

We're sorry to hear your team is encountering this issue. If anyone on your team recalls how you encountered this scenario, we encourage you to open a case with IBM Support. We would be keen look into the matter so we can ensure no other customers encounter it in the future. 

By the CTRL . properties, I presume you are referencing the 'Data source' properties that includes the source data module's path, Id, and other details? The attached screenshot is from 11.1.7. The combination of the Path and Id should be unique to each individual source, even if all the copies of the data modules being used have the same name.

If it helps to reduce work, the option to 'Remove' a data module from the Sources pane is only available when none of the data from that source is being used in the dashboard (on visualizations, in filters etc).

We currently do not have a solution that provides a holistic overview of what data on the dashboard maps to source. It is only available on a per-visualization basis. We would be interested in hearing any suggestions you have to improve this experience. We encourage you and your team to create Ideas in Aha for any suggestions you may have.



------------------------------
Brennan Fox

Product Quality @ IBM Cognos Analytics
------------------------------

Original Message:
Sent: Tue February 02, 2021 10:44 AM
From: Robert Hofstetter
Subject: Dashboard with multiple connections to the same data module

Our developers worked in parallel to develop a dashboard by working independently on their own copies. They then pulled all the widgets together into one dashboard and now have multiple connections to the same data module. It isn't causing any problems now but there will likely be confusion in the long run when updating the data module and associated widgets. I think what happened is they worked on their own copies of the data module and then pinned widgets before relinking to the primary data module but have asked them to clarify exactly how they did it. I can't seem to be able to tell which widgets are tied to which connection from the ctrl-. properties since they are exactly the same. The only way I can think of to rectify this would be to relink the extra connections to a different module, let widgets break and fix them individually. I think then I would be able to remove the extraneous connections once they are no longer used. Is that really the only way to fix this?

------------------------------
Robert Hofstetter
------------------------------

#CognosAnalyticswithWatson

Brennan,

I met with the lead developers yesterday and learned that they had encountered this issue by working independently on copies of the dashboard and then consolidating their work using ctrl-c to copy widgets. One developer had created a local calculation in their copy of the dashboard so even though they were both pointed at the same data module once they pasted the copied widget it had to create a new connection. Interestingly you cannot pin a widget that is based on a local calculation. I think ctrl-c should have resulted in the same error which by the way the error when pinning could have been clearer.

------------------------------
Robert Hofstetter
------------------------------

Original Message:
Sent: Wed February 03, 2021 10:26 AM
From: Brennan Fox
Subject: Dashboard with multiple connections to the same data module

Hi Robert, 

We're sorry to hear your team is encountering this issue. If anyone on your team recalls how you encountered this scenario, we encourage you to open a case with IBM Support. We would be keen look into the matter so we can ensure no other customers encounter it in the future. 

By the CTRL . properties, I presume you are referencing the 'Data source' properties that includes the source data module's path, Id, and other details? The attached screenshot is from 11.1.7. The combination of the Path and Id should be unique to each individual source, even if all the copies of the data modules being used have the same name.

If it helps to reduce work, the option to 'Remove' a data module from the Sources pane is only available when none of the data from that source is being used in the dashboard (on visualizations, in filters etc).

We currently do not have a solution that provides a holistic overview of what data on the dashboard maps to source. It is only available on a per-visualization basis. We would be interested in hearing any suggestions you have to improve this experience. We encourage you and your team to create Ideas in Aha for any suggestions you may have.

------------------------------
Brennan Fox

Product Quality @ IBM Cognos Analytics

Original Message:
Sent: Tue February 02, 2021 10:44 AM
From: Robert Hofstetter
Subject: Dashboard with multiple connections to the same data module

Our developers worked in parallel to develop a dashboard by working independently on their own copies. They then pulled all the widgets together into one dashboard and now have multiple connections to the same data module. It isn't causing any problems now but there will likely be confusion in the long run when updating the data module and associated widgets. I think what happened is they worked on their own copies of the data module and then pinned widgets before relinking to the primary data module but have asked them to clarify exactly how they did it. I can't seem to be able to tell which widgets are tied to which connection from the ctrl-. properties since they are exactly the same. The only way I can think of to rectify this would be to relink the extra connections to a different module, let widgets break and fix them individually. I think then I would be able to remove the extraneous connections once they are no longer used. Is that really the only way to fix this?

------------------------------
Robert Hofstetter
------------------------------

#CognosAnalyticswithWatson

Hi Robert, thank you for the follow up.

I agree, our error messages have room to improve. 

I would recommend opening two separate cases with IBM Support:
1) For the multiple, overlapping data modules situation that came to be because of copying and pasting

2) For the Pinning error message that should be clearer

Having feedback on these matters from a customer like yourself will help the issues get the attention they deserve so that others do not encounter the same challenges in the future. 

------------------------------
Brennan Fox

Product Quality @ IBM Cognos Analytics
------------------------------

Original Message:
Sent: Fri February 05, 2021 11:13 AM
From: Robert Hofstetter
Subject: Dashboard with multiple connections to the same data module

Brennan,

I met with the lead developers yesterday and learned that they had encountered this issue by working independently on copies of the dashboard and then consolidating their work using ctrl-c to copy widgets. One developer had created a local calculation in their copy of the dashboard so even though they were both pointed at the same data module once they pasted the copied widget it had to create a new connection. Interestingly you cannot pin a widget that is based on a local calculation. I think ctrl-c should have resulted in the same error which by the way the error when pinning could have been clearer.

------------------------------
Robert Hofstetter

Original Message:
Sent: Wed February 03, 2021 10:26 AM
From: Brennan Fox
Subject: Dashboard with multiple connections to the same data module

Hi Robert, 

We're sorry to hear your team is encountering this issue. If anyone on your team recalls how you encountered this scenario, we encourage you to open a case with IBM Support. We would be keen look into the matter so we can ensure no other customers encounter it in the future. 

By the CTRL . properties, I presume you are referencing the 'Data source' properties that includes the source data module's path, Id, and other details? The attached screenshot is from 11.1.7. The combination of the Path and Id should be unique to each individual source, even if all the copies of the data modules being used have the same name.

If it helps to reduce work, the option to 'Remove' a data module from the Sources pane is only available when none of the data from that source is being used in the dashboard (on visualizations, in filters etc).

We currently do not have a solution that provides a holistic overview of what data on the dashboard maps to source. It is only available on a per-visualization basis. We would be interested in hearing any suggestions you have to improve this experience. We encourage you and your team to create Ideas in Aha for any suggestions you may have.

------------------------------
Brennan Fox

Product Quality @ IBM Cognos Analytics

Original Message:
Sent: Tue February 02, 2021 10:44 AM
From: Robert Hofstetter
Subject: Dashboard with multiple connections to the same data module

Our developers worked in parallel to develop a dashboard by working independently on their own copies. They then pulled all the widgets together into one dashboard and now have multiple connections to the same data module. It isn't causing any problems now but there will likely be confusion in the long run when updating the data module and associated widgets. I think what happened is they worked on their own copies of the data module and then pinned widgets before relinking to the primary data module but have asked them to clarify exactly how they did it. I can't seem to be able to tell which widgets are tied to which connection from the ctrl-. properties since they are exactly the same. The only way I can think of to rectify this would be to relink the extra connections to a different module, let widgets break and fix them individually. I think then I would be able to remove the extraneous connections once they are no longer used. Is that really the only way to fix this?

------------------------------
Robert Hofstetter
------------------------------

#CognosAnalyticswithWatson

I assume that the developers have used pins to try and move objects from one dashboard to another.  
Have you tried copying instead? 
You could try and fix the issue by deleting the bad visualisations, and then copying them from the source dashboard to the master dashboard.
Pins are great for non developers/authors. Copy / Paste seems to give more 'expected' results for developers.
Just beware that Copy/Paste is limited to the same browser.

------------------------------
Marc Reed
------------------------------

Original Message:
Sent: Tue February 02, 2021 10:44 AM
From: Robert Hofstetter
Subject: Dashboard with multiple connections to the same data module

Our developers worked in parallel to develop a dashboard by working independently on their own copies. They then pulled all the widgets together into one dashboard and now have multiple connections to the same data module. It isn't causing any problems now but there will likely be confusion in the long run when updating the data module and associated widgets. I think what happened is they worked on their own copies of the data module and then pinned widgets before relinking to the primary data module but have asked them to clarify exactly how they did it. I can't seem to be able to tell which widgets are tied to which connection from the ctrl-. properties since they are exactly the same. The only way I can think of to rectify this would be to relink the extra connections to a different module, let widgets break and fix them individually. I think then I would be able to remove the extraneous connections once they are no longer used. Is that really the only way to fix this?

------------------------------
Robert Hofstetter
------------------------------

#CognosAnalyticswithWatson