I’m building an app that involves copying items from one board to another using the Monday.com API. I’ve been experimenting with the duplicate_item mutation, and while it seems to support cross-board duplication (even though this isn’t clearly documented), I’m running into an issue:
The main item gets successfully copied to the target board, but the subitems do not.
Has anyone else experienced this?
Is this expected behavior?
Is there a recommended way to include subitems during cross-board duplication?
Any official word on whether duplicate_item is intended to support this use case?
Appreciate any insight or confirmation from others in the community or the Monday team.
Hey, I ran into this too while building a content ops tool for our casino team using Monday.com – looks like duplicate_item skips subitems when copying across boards since subitems live on a separate internal board. What worked for me was grabbing the subitems with a query and recreating them manually with create_subitem after the main item gets duplicated. Not super elegant but gets the job done. Would love an official fix though – anyone from the team got insight?
Earlier I was duplicating an item in the current board with duplicate_item mutation and then moving it to the target board. But it’s not reliable as sometimes the sub items doesn’t get created and item move gets done.
Stay away from that mutation for cross-board duplication!!! We had been using it for a few years and it worked great. Unfortunately in an API update last fall, Monday figured out cross-board was possible and that it shouldn’t have been allowed. They “fixed” it and completely broke a mission-critical communication tool on our end.
We now do a same board duplication and then move it to the new board. It is not nearly as elegant and we run into issues with one operation not releasing the lock on the item before the next operation tries to grab the item. We’ve had to build in a 5 second delay to keep the race condition from happening.
This is a bummer, thanks for letting me know this.
I already did the implimentation depending the mutation duplicate_item to duplicate it in another board. Seems like will have to revert it then.
TBH it’s just a hack and not really a better solution. But atleast it’s not reliable and won’t break in production.
The current approach of duplicating in the same board and moving to the target board is quite clankly specially if you need sub items and updates copy as well.
