Skip to main content
Question

Best practice to manage graphql ids

  • July 6, 2026
  • 0 replies
  • 19 views

Hi everyone,

I'm looking for some advice on a challenge we're currently facing.

Our app has two form-based features:

  • Feature #1 generates boards and columns using the monday.com GraphQL API. We currently store the generated board and column IDs using the monday.storage() SDK method.

  • Feature #2 uses those stored GraphQL IDs to create new items, since the app is connected to the generated boards and columns through those IDs.

The challenge arises when we need to update the board structure after the app has already been installed. For example, if we decide to add a new column to the generated board in a future release, the ID of that newly created column won't exist in the user's existing monday.storage() data. As a result, Feature #2 won't be aware of the new column unless the stored IDs are updated.

For those who have built similar apps, how do you manage GraphQL IDs for dynamically generated boards and columns? Do you have a strategy for handling schema changes (such as adding new columns) while ensuring existing installations stay in sync?

I'd appreciate any recommendations or best practices. Thanks!