Hi all,

Wondering if there's a way to rename a data module without impacting the source identifier? For instance, if I have a model named Call center the source identifier would be C_Call_Center. But if I want to save it with a new name, such as Call Center Global, the source identifier will change.

If I want to repoint any reports from the original model to the new model they will not validate. If I examine the query item expression definition I would see something like this: [C].[C_Call_Center].[Table_123.[Column_ABC]. But instead Cognos expects this: [C].[C_Call_Center_Global].[Table_123.[Column_ABC]. I know I can remove the source identifier so it would instead be [Table_123.[Column_ABC].

I'm just trying to figure out if there's a less cumbersome way to do things. I imagine I just don't know how. :)

Thanks!

------------------------------
Jeremy Aude
------------------------------

#CognosAnalyticswithWatson

Hi Jeremy,

I guess you shoud try to use the "CTRL" + "/" + "Q" shortcut to edit the new data module and replace the name with the original one.

I don't see other solutions at this point.

Best regards,

------------------------------
Patrick Neveu
Positive Thinking Company
------------------------------

Original Message:
Sent: Thu September 01, 2022 02:02 PM
From: Jeremy Aude
Subject: Rename Data Module

Hi all,

Wondering if there's a way to rename a data module without impacting the source identifier? For instance, if I have a model named Call center the source identifier would be C_Call_Center. But if I want to save it with a new name, such as Call Center Global, the source identifier will change.

If I want to repoint any reports from the original model to the new model they will not validate. If I examine the query item expression definition I would see something like this: [C].[C_Call_Center].[Table_123.[Column_ABC]. But instead Cognos expects this: [C].[C_Call_Center_Global].[Table_123.[Column_ABC]. I know I can remove the source identifier so it would instead be [Table_123.[Column_ABC].

I'm just trying to figure out if there's a less cumbersome way to do things. I imagine I just don't know how. :)

Thanks!

------------------------------
Jeremy Aude
------------------------------

#CognosAnalyticswithWatson

If I understand correctly, you have created some reports, renamed the module which is used in the reports, and when you edit or try to run the reports you get errors.  When you edit the report specification and replace the references to the old module with the new module name are you able to proceed?

------------------------------
IAN HENDERSON
------------------------------

Original Message:
Sent: Thu September 01, 2022 02:02 PM
From: Jeremy Aude
Subject: Rename Data Module

Hi all,

Wondering if there's a way to rename a data module without impacting the source identifier? For instance, if I have a model named Call center the source identifier would be C_Call_Center. But if I want to save it with a new name, such as Call Center Global, the source identifier will change.

If I want to repoint any reports from the original model to the new model they will not validate. If I examine the query item expression definition I would see something like this: [C].[C_Call_Center].[Table_123.[Column_ABC]. But instead Cognos expects this: [C].[C_Call_Center_Global].[Table_123.[Column_ABC]. I know I can remove the source identifier so it would instead be [Table_123.[Column_ABC].

I'm just trying to figure out if there's a less cumbersome way to do things. I imagine I just don't know how. :)

Thanks!

------------------------------
Jeremy Aude
------------------------------

#CognosAnalyticswithWatson

Hi @IAN HENDERSON,

Apologies for the late response. Yes, I get the errors after renaming a data module. I am able to run after updating the report specification.

When using reports against a Framework Manager package I can repoint to a new package name as long as the [Namespace].[Query Subject].[Query Item] naming remains unchanged.

I know the report specification update is the solution, but I'm just wondering if there is an easier way to accomplish this task.


Thanks,
Jeremy

------------------------------
Jeremy Aude
------------------------------

Original Message:
Sent: Fri September 02, 2022 10:29 AM
From: IAN HENDERSON
Subject: Rename Data Module

If I understand correctly, you have created some reports, renamed the module which is used in the reports, and when you edit or try to run the reports you get errors.  When you edit the report specification and replace the references to the old module with the new module name are you able to proceed?

------------------------------
IAN HENDERSON

Original Message:
Sent: Thu September 01, 2022 02:02 PM
From: Jeremy Aude
Subject: Rename Data Module

Hi all,

Wondering if there's a way to rename a data module without impacting the source identifier? For instance, if I have a model named Call center the source identifier would be C_Call_Center. But if I want to save it with a new name, such as Call Center Global, the source identifier will change.

If I want to repoint any reports from the original model to the new model they will not validate. If I examine the query item expression definition I would see something like this: [C].[C_Call_Center].[Table_123.[Column_ABC]. But instead Cognos expects this: [C].[C_Call_Center_Global].[Table_123.[Column_ABC]. I know I can remove the source identifier so it would instead be [Table_123.[Column_ABC].

I'm just trying to figure out if there's a less cumbersome way to do things. I imagine I just don't know how. :)

Thanks!

------------------------------
Jeremy Aude
------------------------------

#CognosAnalyticswithWatson

Updating the report specifications is a suitable solution for a few reports. If we use Data Modules as a replacement for FWM then updating report specs won't be a suitable option. 
I found a lot of similar issues when using data modules derived from the naming that I've never experienced with the FWM. I mostly rely on company-curated FWM models so I don't use Data Modules often enough to keep track of the annoyances

------------------------------
Mauro Santos Otero
------------------------------

Original Message:
Sent: Tue September 20, 2022 10:30 AM
From: Jeremy Aude
Subject: Rename Data Module

Hi @IAN HENDERSON,

Apologies for the late response. Yes, I get the errors after renaming a data module. I am able to run after updating the report specification.

When using reports against a Framework Manager package I can repoint to a new package name as long as the [Namespace].[Query Subject].[Query Item] naming remains unchanged.

I know the report specification update is the solution, but I'm just wondering if there is an easier way to accomplish this task.


Thanks,
Jeremy

------------------------------
Jeremy Aude

Original Message:
Sent: Fri September 02, 2022 10:29 AM
From: IAN HENDERSON
Subject: Rename Data Module

If I understand correctly, you have created some reports, renamed the module which is used in the reports, and when you edit or try to run the reports you get errors.  When you edit the report specification and replace the references to the old module with the new module name are you able to proceed?

------------------------------
IAN HENDERSON

Original Message:
Sent: Thu September 01, 2022 02:02 PM
From: Jeremy Aude
Subject: Rename Data Module

Hi all,

Wondering if there's a way to rename a data module without impacting the source identifier? For instance, if I have a model named Call center the source identifier would be C_Call_Center. But if I want to save it with a new name, such as Call Center Global, the source identifier will change.

If I want to repoint any reports from the original model to the new model they will not validate. If I examine the query item expression definition I would see something like this: [C].[C_Call_Center].[Table_123.[Column_ABC]. But instead Cognos expects this: [C].[C_Call_Center_Global].[Table_123.[Column_ABC]. I know I can remove the source identifier so it would instead be [Table_123.[Column_ABC].

I'm just trying to figure out if there's a less cumbersome way to do things. I imagine I just don't know how. :)

Thanks!

------------------------------
Jeremy Aude
------------------------------

#CognosAnalyticswithWatson

Original Message:
Sent: 9/21/2022 1:50:00 AM
From: Mauro Santos Otero
Subject: RE: Rename Data Module

Updating the report specifications is a suitable solution for a few reports. If we use Data Modules as a replacement for FWM then updating report specs won't be a suitable option. 
I found a lot of similar issues when using data modules derived from the naming that I've never experienced with the FWM. I mostly rely on company-curated FWM models so I don't use Data Modules often enough to keep track of the annoyances

------------------------------
Mauro Santos Otero
------------------------------

Original Message:
Sent: Tue September 20, 2022 10:30 AM
From: Jeremy Aude
Subject: Rename Data Module

Hi @IAN HENDERSON,

Apologies for the late response. Yes, I get the errors after renaming a data module. I am able to run after updating the report specification.

When using reports against a Framework Manager package I can repoint to a new package name as long as the [Namespace].[Query Subject].[Query Item] naming remains unchanged.

I know the report specification update is the solution, but I'm just wondering if there is an easier way to accomplish this task.


Thanks,
Jeremy

------------------------------
Jeremy Aude

Original Message:
Sent: Fri September 02, 2022 10:29 AM
From: IAN HENDERSON
Subject: Rename Data Module

If I understand correctly, you have created some reports, renamed the module which is used in the reports, and when you edit or try to run the reports you get errors.  When you edit the report specification and replace the references to the old module with the new module name are you able to proceed?

------------------------------
IAN HENDERSON

Original Message:
Sent: Thu September 01, 2022 02:02 PM
From: Jeremy Aude
Subject: Rename Data Module

Hi all,

Wondering if there's a way to rename a data module without impacting the source identifier? For instance, if I have a model named Call center the source identifier would be C_Call_Center. But if I want to save it with a new name, such as Call Center Global, the source identifier will change.

If I want to repoint any reports from the original model to the new model they will not validate. If I examine the query item expression definition I would see something like this: [C].[C_Call_Center].[Table_123.[Column_ABC]. But instead Cognos expects this: [C].[C_Call_Center_Global].[Table_123.[Column_ABC]. I know I can remove the source identifier so it would instead be [Table_123.[Column_ABC].

I'm just trying to figure out if there's a less cumbersome way to do things. I imagine I just don't know how. :)

Thanks!

------------------------------
Jeremy Aude
------------------------------

#CognosAnalyticswithWatson

Yes, I experienced a similar issue before with Data Modules.  Changing names creates huge issues. That's the reason Framework Manager is still better.

------------------------------
Mauro Santos Otero
------------------------------

Original Message:
Sent: Thu September 01, 2022 02:02 PM
From: Jeremy Aude
Subject: Rename Data Module

Hi all,

Wondering if there's a way to rename a data module without impacting the source identifier? For instance, if I have a model named Call center the source identifier would be C_Call_Center. But if I want to save it with a new name, such as Call Center Global, the source identifier will change.

If I want to repoint any reports from the original model to the new model they will not validate. If I examine the query item expression definition I would see something like this: [C].[C_Call_Center].[Table_123.[Column_ABC]. But instead Cognos expects this: [C].[C_Call_Center_Global].[Table_123.[Column_ABC]. I know I can remove the source identifier so it would instead be [Table_123.[Column_ABC].

I'm just trying to figure out if there's a less cumbersome way to do things. I imagine I just don't know how. :)

Thanks!

------------------------------
Jeremy Aude
------------------------------

#CognosAnalyticswithWatson