Deprecation is a controlled retirement mechanism. When Epic deprecates a Clarity column, the column remains defined in the table so that existing reports, views and queries that reference it continue to compile and run without error. What changes is the extract: the column no longer receives new data, so it returns NULL for rows loaded after the deprecation, while historical values may remain for older rows depending on the table. This is the pattern behind a report that silently returns blanks after an upgrade, and it is why the Data Dictionary displays a Deprecated indicator on affected columns. Rows are not removed, because deprecation applies to a column and does not delete data. The column is not announced for deletion in a future version as a rule, so that option over-states the policy. Reassigning the column to a different Chronicles item would corrupt the meaning of existing reports and is the opposite of what deprecation is designed to prevent. The practical response is to read the column description for the recommended replacement and revise dependent queries. Treating a deprecated column as unreliable for new data, while understanding that it will not generate an error, is the behavior the certification expects analysts to recognize.
[Reference: Cogito Fundamentals – Clarity Data Model: Deprecated Columns; Data Dictionary, ===============, ]
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit