In SAS Viya, user-defined formats are no longer just simple catalog entries; they must exist in the right memory space to work correctly.
The "Split Brain" Risk: A format stored only in a local SAS catalog (on the Compute Server) will work fine for PROC PRINT, but will fail (display raw values) if you try to use it inside a CAS action (like cardinality.summarize).
The Solution: You must explicitly load your formats into a CAS Format Library. This pushes the mapping logic up to the CAS server, allowing distributed worker nodes to apply the labels during parallel processing.
Scope Matters: By default, a format loaded into CAS is "Session-Scope" (visible only to you, for now). Use the promote action to make it "Global-Scope," ensuring other users and scheduled jobs can see the same data definitions without reloading them.