One way relationship requirements for required custom fields
Austin Hodges
Currently. when creating custom fields that are required in a list/folder/space, when setting a relationship field as required, it creates the requirement in the other side as well.
When enabling 'Required in tasks' on one side of the relationship, the other side is also required.
For instance. I have a Contacts and Customers lists. I also have a billing list. When creating tasks on the billing list, I want to be able to require a contact task and customer task to create the billing task, BUT, when creating a new contact task or customer task, I don't want to also have to add a billing task because this customer doesn't have any billing tasks yet.
It would be very nice to be able to create a one-way specific relationship requirement in a list that only affects that list and not the related tasks.
Log In