Hi Michael,
actually that's the way I do it all the time - I'm lazy ;). I only update FM models when important changes have applied to the tables.
Why should Cognos cut the value of a column value? It's basically an SQL generator and displays the result set. The system does not check the length of a column with the acutal value as far as I know. It's more important to set the usage, aggregate types and determinants of your query items & subjects. That's what Cognos really needs to know to build the query.
Sometimes Cognos generates SQL with CAST() used. Maybe then it is more important to have the right precision for the field in your model...
------------------------------
Robert Dostal
Principal Expert BI
GEMÜ Gebr. Müller Apparatebau GmbH & Co. KG
Kupferzell
------------------------------
Original Message:
Sent: Tue September 16, 2025 01:30 PM
From: Michael Sullivan
Subject: Unexpected behavior - full column value displays despite FM values
Hi everyone,
Can anyone explain why the following worked?
We lengthened a field in an Oracle table that is a data source for one of our Framework Manager data source query subjects (that feeds model query subjects and then gets published as packages and used in Cognos reports)
However, we did not alter the scale or precision of the column in Framework Manager
Nor did we republish anything
Yet, to our surprise, longer values (than would seem to fit in the column) are displayed in reporting
Why would that be?
Here are two pictures. The first from Framework Manager, the second from a Cognos report. The number is bogus
Thanks for any thoughts!
Mike
-- Michael Sullivan
978 762 4218
North Shore Community College