Issues with Blueprints and custom fields

Hi team, I was speaking with my account rep on an issue with Blueprints and we identified that when creating a Blueprint from a task, it will save any custom fields existing before the BP was created. This is good, because I thought it didn't, so I was creating templates as regular tasks (because I needed this custom field functionality).

However the issue we identified is that once it's a Blueprint, you can't edit the fields, and you can't see any fields, this is why I was confused. So good news, but also bad news, because if I have to make a change to the custom field  in future, I have to recreate the Blueprint as a regular task, edit it, then resave as a Blueprint, then reconnect it in any forms it is being used (tedious).

If a Blueprint has custom fields you should be able to see it and edit it in the task view.

Upvote 2
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
3 commentaires

Hi @Austin Headley,

One thing I've learned about Wrike custom fields is that they're always there in the background and only visible if you've assigned them to the containing folder.

In your case, you should be able to add your existing custom field definitions to the folder your blueprints are in to be able to see and edit them on the blueprints. https://help.wrike.com/hc/en-us/articles/1500005219262-Adding-Custom-Fields-to-Folders-Projects-or-Spaces

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Actually figured this one out - it's not showing in Blueprints because I had to manually add the fields to the folder! Oops. 

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Issues with Blueprints and custom fields
[this list is visible for admins and agents only]

Haut de la page
Didn’t find what you were looking for? Write new post