In our Monday.com set up we have multiple boards that need to move their items to a consolidated board. You can see it as many child boards “promoting” their items to a consolidated board.
Currently what I have done is to create the boards so that all the columns and the column ids are the same to make it easy to manage.
I have a Monday GraphQL module with a move_item_to_board mutation that maps all child items to the consolidated board. For columns we don’t want to migrate over, I map these to null.
The challenge is that it restricts our users on adding columns, as soon as they do the mutation fails as there is no mapping for the new column. Are there any suggestions on how I can overcome this?
I have thought about keeping a data store of all child board and consolidated board column ids and marking them as “to be copied or not”, but then I am not sure how to dynamically create the graphql to move the item. I.e. I could have one webhook to update the table when a column is created and then another webhook to move the item when needed. In this second scenario I would need to generate the script.
Thank you for any help and direction.