Prepare a member or hierarchy change

Replace the placeholders with values from your own authorized scope before copying this prompt into an MCP client.

Inputs

• {{workspace_id}} Stable workspace ID.
• {{application_id}} Stable application ID.
• {{dimension_id}} Target dimension ID.
• {{requested_change}} Exact requested member or parent–child change.
• {{metadata_revision}} Current integer metadataRevision from application.state.read.

Prompt

Read the current metadata revision and target members and relationships in {{workspace_id}} / {{application_id}} for dimension {{dimension_id}}.
Prepare {{requested_change}} as a proposed metadata.member.create or metadata.relationship.create program for execute_v2_metadata_program.
For a proposed link, verify both active endpoints, check the relationship ID and parent–child pair for duplicates, and check the active edges for a path from the proposed child to the proposed parent.
Return the proposed program and revision fence for review.
Stop before execution or when required IDs or the relationship path cannot be verified.

Example inputs

Use the active members and edges from the Account inspection example. In the disposable cube, draft a link from Metrics to Calculated. Confirm both exist and that Calculated cannot already reach Metrics. Review the resulting rollup impact and return the draft without submitting it.

{
  "languageVersion": 2,
  "function": "metadata.relationship.create",
  "arguments": {
    "dimensionId": "Account",
    "relationshipId": "docs.metrics-calculated",
    "parentMemberId": "Metrics",
    "childMemberId": "Calculated",
    "expectedMetadataRevision": {{metadata_revision}}
  }
}

Tools used include read_v2_program, execute_v2_metadata_program. See the module guidelines and tool index.