Model metadata and calendars

Inspect dimensions, members, attributes and relationships from an authorized application scope. Resolve stable IDs and retain the metadata revision. To make a change, verify that the catalog grants the specific metadata or calendar write you intend to perform.

Read the model before preparing changes

1. Inspect a dimension with read_v2_program. Resolve the dimension, then page its members and active relationships at the same metadata revision. In the sample, Account member InputA has Behavior Input.
2. Prepare a hierarchy change by verifying both stable member IDs and checking for an existing edge or a cycle. The sample drafts a Metrics to Calculated edge and stops before submission.
3. To create a member list, save an immutable definition through execute_v2_metadata_program. Read back the exact version and digest. Saved is the expected stop point in the sample. Publication is separate.
4. Configure a calendar period using active Year and Period IDs, a period ordinal and an inclusive start with exclusive end. For Y2027 and P01, the sample reads back [2027-01-01, 2027-02-01) and the new change ID.

If the metadata revision changes during paging or review, reread the affected scope and rebuild the change from the current state. A stale calendar change ID, overlap or ordinal conflict requires a fresh read before another write.

Metadata prompt templates · Metadata and calendar tools