PeterS Posted November 6, 2018 Report Share Posted November 6, 2018 I have a enumerator, single selection custom attribute on all my projects. It has a default value set. Users must be able to change the value of this custom attribute. Is there a way to avoid the attribute having no value? ATM a user can delete the value and the attribute is being stored with no set value. Any way to configure my custom attribute in a way that a value is mandatory? Thanks Link to comment Share on other sites More sharing options...
Mattias Lagergren Posted November 12, 2018 Report Share Posted November 12, 2018 Hi Peter, I'm afraid it is not possible to set the custom attribute to mandatory. But I think it makes sense and will raise it as a feature request with the team Link to comment Share on other sites More sharing options...
Guest Posted November 12, 2018 Report Share Posted November 12, 2018 Hi Peter, If you or someone on your team is comfortable working with the API and running an event listener, it would be possible to respond to a user's deleting the value. You could revert to the previous value, set it to a default, or prompt the user to set it themselves. Here's a similar example to get you started--reverting status changes by users not in a certain group. https://bitbucket.org/snippets/ftrack/LEx77/event-listener-restrict-task-status Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.