Hello,
Short story:
I’ve created a new board template and I’m having trouble creating a new board with that template via the API. Using the template ID shown in the template center, the create_board mutation throws a “CreateBoardException” with status code 400.
Long story:
Long ago, I created some board templates and have been using them since without issue. These old board templates are located in a workspace with non-template boards (in addition to the template center) and have a 9 digit ID number like any other board, only with a wand icon. I am able to create a new board using the create_board mutation and this ID. Editing the template from the template center takes me directly to the template board in its workspace, and the template retains its original template ID.
Now, when I create a new board template it’s moved out of its workspace and into the template center. This new template has an 8 digit template ID in the template center. This is the ID that throws the “CreateBoardException” when using the the create_board mutation.
Editing this template from the template center takes me to a new space different than the old templates. Instead of editing the single board, it looks like you can add multiple boards, docs, etc to this one template. And, publishing any edits changes the template ID(!?)
How do I create a board using these newer templates through the API? Am I using the wrong template ID?
Would you be able to please fill this form adding as much information as possible to it (such as account ID, board IDs, item IDs, timestamps, etc.) so that our team can take a look into it? A screen recording would be fantastic! You can use Loom (it is free).
When I create a board via the API using old templates, it works.
When I take the template ID from the Template center for a new template (one that does not exist as a board in the workspace with a wand but only as a template in the template center) I get the following error:
I believe I misunderstood when I read your comment and now understand the issue after @Irit 's message.
You can not use this mutation for board templates that are not part of your account. You would need to first create a board from the template from the templates center, and then save that new board as a “template” and then use that new board’s ID in your mutation.
@Matias.Monday I created a board and then saved it as a template. It lives in the template center.
But I can’t use the ID (taken from the template center URL) in an API call to create a board.
I don’t see a way to create a template from within the template center.
I have also tried the following:
Creating a board
Saving as a template
Creating another board from the template
Saving that board as a template
That is my bad. I now realize you have the new UI regarding the templates in your account (it is not available to everyone yet).
As of today, you can not use the create_board mutation with one of those templates. You would need to use a regular board (that is not a template) and duplicate said board via API using the duplicate_board mutation.
Ahhhhh so instead of using a template I have to duplicate a board.
Now I have the issue of recalculating all dates.
Will figure it out.
Thanks for the update.
I have the same problem. Is there a way to turn off the new template center? This update means I would need to maintain a template in the center and a template board…
I’m trying to use the boardMapping field in a recipe, and the template ID returned for SOME templates doesn’t work with the create_board mutation. Others (the really basic ones) seem to. But many if not most of the templates do not.
It seems to be dependent on the “isSolution” of the boardMapping being true - but I cannot confirm this.
Yeah its broken and they so far seem to refuse to acknowledge it is still broken when you contact support. Just throw up roadblocks to make you go away, wanting screen shots and screen recordings - of an API call anyone can make.
Hey sorry Cody I missed your reply earlier. It works well for me when I use the template ID found on the template center when you have developer mode enabled, but in your case it might be a account-specific issue. Typically when I speak to monday support I ask them to escalate when I feel the way you do and they’re usually helpful and do it on request.
Right, but our marketplace app customers aren’t going to turn on developer mode, find a template ID in the template center, go create a recipe and type in the template ID to make our app feature work. That being a viable solution for a marketplace app is an asinine proposition.
The field monday provides to developers for use in integration actions, for the user to pick a template, sends a template ID that doesn’t work with the API for all but a handful of the selections presented.
Developer support can’t get past the basics “the template must be in your account”. Fine. But the template selection field for recipes is showing templates the users can pick but don’t work if we use the template ID sent in the action. It is broken. Support can’t grok that. I gave up and cancelled the feature from my app since monday won’t acknowledge something is obviously still broken - I can’t rely on it and release a feature which is going to cause end users a terrible and unreliable experience.