Skip to content

BINFR-6469: identify view bookmarks by node.key instead of boardId#387

Closed
Manjinder Singh (manjindersingh98) wants to merge 2 commits into
mainfrom
binfr-6469-bookmarks-node-key
Closed

BINFR-6469: identify view bookmarks by node.key instead of boardId#387
Manjinder Singh (manjindersingh98) wants to merge 2 commits into
mainfrom
binfr-6469-bookmarks-node-key

Conversation

@manjindersingh98

@manjindersingh98 Manjinder Singh (manjindersingh98) commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

What & why

The blueprint bookmark import/export endpoints now key off the stable node key (rootNodeKey + key) instead of boardId, which is regenerated during a team-to-team copy. This updates the view-bookmarks commands accordingly so the same command works across teams (e.g. after a T2T copy).

Changes

  • pull view-bookmarks / push view-bookmarks: replace --id <boardId> with required --rootNodeKey <rootNodeKey> and --key <key>.
  • Build request URLs with rootNodeKey + key params; name the export file studio_view_bookmarks_<rootNodeKey>.<key>.json.
  • Threaded the new params through the command service, manager-factory, and manager.
  • Updated docs and unit tests.

⚠️ Breaking change

Requires the matching blueprint endpoint change (celonis/blueprint#3234) — must be released together.

Out of scope

Analysis bookmarks (pull/push bookmarks) hit process-analytics, not blueprint — unchanged.

Testing

npx jest tests/commands/view (8 passing); tsc --noEmit clean.

Jira: BINFR-6469 (epic BINFR-6385)

🤖 Generated with Claude Code


Note

Medium Risk
Breaking CLI contract and coordinated release with blueprint; scope is limited to view-bookmarks only.

Overview
Breaking change: pull view-bookmarks and push view-bookmarks no longer accept --id (board UUID). They now require --rootNodeKeyWithBoardKey and --key so views are addressed by stable Studio node keys that survive team-to-team copies.

Blueprint bookmark import/export URLs are built with rootNodeKeyWithBoardKey and key query params instead of boardId. Pulled files are named studio_view_bookmarks_<rootNodeKeyWithBoardKey>.<key>.json. The same parameters are threaded through the CLI module, command service, manager factory, and manager; user docs and view command tests are updated to match.

This must ship together with the matching blueprint API change; analysis bookmark commands are unchanged.

Reviewed by Cursor Bugbot for commit 879cab3. Bugbot is set up for automated code reviews on this repo. Configure here.

The blueprint bookmark import/export endpoints now key off the stable node
key (rootNodeKey + key) instead of the boardId, which is regenerated during a
team-to-team copy. Update the view-bookmarks pull/push commands to pass
--rootNodeKey and --key, build the request URLs with those params, and name the
export file after the node key. Requires the matching blueprint change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Match the blueprint endpoint rename: the view-bookmarks commands now use a
--rootNodeKeyWithBoardKey flag and send it as the rootNodeKeyWithBoardKey query
param alongside --key. Both parts are required since a board key is not unique
across teams.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@manjindersingh98

Copy link
Copy Markdown
Contributor Author

I'm closing the PR as Roberto Welzel Filho (@roberto-welzel) is going forward with an asset Id to key map to solve the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant