Introduction › Changing the Status of a Dataview Definition › Status for Unmodeled Dataviews

Status for Unmodeled Dataviews

Although dataviews are an extension of the data model, CA Ideal enforces the version and status for unmodeled dataviews, not the dictionary. For unmodeled dataviews, the entity‑occurrence is stored in the dictionary in test status, but CA Ideal enforces production and history restrictions based on a value recorded in the ACCESS‑CODE field in the dictionary. Thus, if a production and a test version exist for an unmodeled dataview, there are actually two test versions in the dictionary, one with an ACCESS‑CODE of PROD and one with an ACCESS‑CODE of TEST.