Data module-Could not load grid data: Data source was not found in Content store

[cognosjon]

Hi,
we are having some issues when creating a data module using a published package. We can select the package with no issues, but when trying to create a relationship we are presented with the following message.

Could not load grid data: Data source "xxx" was not found in Content Manager.

We are able to use this package to run reports and dashboards with no issues but not data modules. Other packages do function as expected.
I have tried recreating the connection but the issue still exists.
Any thoughts?

Thanks ini advance

[MFGF]

Hi,
we are having some issues when creating a data module using a published package. We can select the package with no issues, but when trying to create a relationship we are presented with the following message.

Could not load grid data: Data source "xxx" was not found in Content Manager.

We are able to use this package to run reports and dashboards with no issues but not data modules. Other packages do function as expected.
I have tried recreating the connection but the issue still exists.
Any thoughts?

Thanks ini advance

Hi Jon,

Is the package published in Dynamic Query Mode?

Cheers!

MF.

[cognosjon]

Morning,

Good point!!

No this package is not currently DQM. I'll give that a try. Out of interest one of my other packages that does work is also not yet DQM.

I'll give it a go.

[MFGF]

Morning,

Good point!!

No this package is not currently DQM. I'll give that a try. Out of interest one of my other packages that does work is also not yet DQM.

I'll give it a go.

I think that for dashboards and data modules there's an attempt to convert on-the-fly behind the scenes if you use a CQM package. This isn't always successful, depending on what's going on in the underlying FM model that was used to publish the package.

The safe and supported way is to convert your package to DQM (fixing any issues at the same time) then use the new DQM package in your dashboard/data module :)

Cheers!

MF.

[cognosjon]

After multiple attempts at playing around with the FM model, changing it to DQM etc ( which unfortunately did not resolve the problem) it would appear that the issue relates to an old Data source connection within our impacted Framework model.

The prospect of recreating the framework terrifies me due to the size of it and its current usage within the business so I was hoping to be able to modify the data source that a query subject has been created against.
However I seem to be struggling with what I thought would be a simple task.

If I double click a query subject to get into edit mode, under the available database objects window I would like to change the source being used. Unfortunately I don't seem able to do this.
Anyone been able to accomplish this? I've tried editing the XML to change the data source but that didn't work either.
I've added an attachment just to show what and where i'm trying to change
Thanks

[bus_pass_man]

it would appear that the issue relates to an old Data source connection within our impacted Framework model.

Just to confirm, the FM model uses a data source connection which doesn't exist?

Switching the data sources used in a FM model is dead easy.   

Select a data source and edit the content manager data source, schema, and catalog properties to use those of the new data source.  If you don't know what values they are, import a table from the data source connection and match those values in the existing data source connection.   You might have a bunch of 'needs reevaluation' statuses, which is easily dealt with by validate selected objects.  You will need to republish the package.

You don't want to muck about editing the query subjects.

I've tried editing the XML to change the data source but that didn't work either.

Do not try to do stuff like this.

[cognosjon]

Just an update to say that I have finally managed to resolve my problem.

The problem encountered was due to an old legacy FM that had been based on multiple datasources, which appear to have once been Oracle based and now SQL. Query subjects were pointed at different datasources which were ultimately the same database and this confusion was leading to Modules and dashboards refusing to speak to it.

Unfortunately Bus_pass it wasn't as straight forward as you detailed ( I wish it had been).  I did end up updating the XML of the model after IBM support had struggled to get their head around it, and they also suggested (although not supported) that the xml route was probably the only option.

MFGF I've also updated these packages to be Dynamic.

Thanks

[MFGF]

Just an update to say that I have finally managed to resolve my problem.

The problem encountered was due to an old legacy FM that had been based on multiple datasources, which appear to have once been Oracle based and now SQL. Query subjects were pointed at different datasources which were ultimately the same database and this confusion was leading to Modules and dashboards refusing to speak to it.

Unfortunately Bus_pass it wasn't as straight forward as you detailed ( I wish it had been).  I did end up updating the XML of the model after IBM support had struggled to get their head around it, and they also suggested (although not supported) that the xml route was probably the only option.

MFGF I've also updated these packages to be Dynamic.

Thanks

Sounds like you had your work cut out there! Well done from me for resolving it :)

Cheers!

MF.