Custom Field populated by Request Form needs to trigger another Custom Field value
Hi Everyone,
I have a situation where I want to populate 2 separate custom fields from one question answered in a request form. Let me explain...
I have a single select field (A) that I am using to answer a request form question. When the project is created this field populates correctly. I set up automations that, based on the value in this field, another custom field (B) rolls up and populates. So, if X specific options of the 12 choices in the list for field A are chosen, then field B will populate with XX. If a Y option is chosen in field A, then field B populates with YY, etc.
If a project already exists and I manually make a choice in field A, the automation works and field B populates. If the request form fills in field A, though, then the request form doesn't see it as a trigger and won't change field B.
Does anyone know a way that I can get this to work? Our request forms have a ton of housekeeping questions and I'd like to reduce the number and prevent question fatigue. Also, a requester may know the answer to field A, but they may not always select the correct option for field B, so I'm trying to eliminate user error here.
Hoping that there is a solution, but if not, then I suggest a new automation trigger to look in a custom field to see if it's populated from a form.
Thanks,
steve
Hi Steve Mruskovic,
I think you can do this by using New Item is created as trigger.
Hi Steve Mruskovic,
What are you using as trigger for your automation rule? Pietro's suggestion won't work If you would change the custom field A manually afterwards, so I'm afraid you have to create another automation rule using this trigger.
Please support this request to be able to use more than one trigger within the same rule: Multiple triggers to create OR / AND logic in Automation? – Wrike Help Center
Florian
Hi Florian Kislich,
I agree Steve needs to create 2 different automations one for item creation and one for change custom field value
Hi Pietro Poli and Florian Kislich, appreciate the responses!
Indeed, following Pietro's solution worked for the initial creation, and the manual option should not happen as frequently as the automated solution, so I think I'm good for now. I'll upvote Florian's link, too, because...reasons!
I still loathe having to trickle these down from project to tasks, but that's a need many of us are still fighting for.
Thanks,
steve