I have a Data Module using tables sourced from a Data Server.
After creating the module the table definition changed in the database for one of tables in the module.
I reloaded the metadata for the schema, edited the data module, and dragged the table into the module from the source. I clicked "yes" on the popup that indicated I'd be re-adding the table.
What resulted was this:
- New columns in the table were added to my module (as expected)
- Data type changes to the existing columns in that table in my module did NOT get reflected in the module.
The data type changes were clearly visible in the properties of columns in the source pane... so I know that the metadata refresh did load the updated definitions.
The work-arounds I've found are (1) to delete those columns from my module, then re-add them from my source, and (2) use Control-q-/ to update the data definitions by hand.
My question for the team is this: Is there an "official way" to refresh all the existing columns in a table in my module so they reflect the data definitions in the loaded metadata short of the 2 hacks I list above?
Thanks! By the way, I've tested both 11.1.5 and 11.1.6, and get the same results (although adding the new columns is easier in 11.1.6).
Rich
------------------------------
Richard Chester
Director of Business Intelligence
LPA Software Solutions
------------------------------
#CognosAnalyticswithWatson