Task name rules based on custom fields not working?

:light_bulb:Hi Asana Forum!

My team is currently working on a Salesforce/Asana integration. We have a project setup where tasks are created when a deal is created or updated in Salesforce. We set up a custom field “Deal Name” that is synced to the deal name in Salesforce. This information consistently pulls in, we have not had any issues with that part.

The issue is, we have a rule that sets the task name based off of the custom field “Deal Name” (screenshot of the rule below), but, for some reason it does not trigger all the time leaving some tasks to be named [no value] despite the “Deal Name” custom field being filled out.

Any tips/tricks would be greatly appreciated!

Hey @Joe_MacKenna I’m pretty what is happening is that your rule for setting the task name is intermittently outpacing the behind the scenes automation that sets the Deal Name custom field to match the deal name in Salesforce. And when that happens, it’s referencing a Deal Name that hasn’t popualted yet, causing the no value.

Since there’s no way in Asana rules to force a delay or to choose what sequence things run, I believe a bandaid you can try (but I’m not entirely sure it will work):slight_smile:

Create another rule that says: (When) Task name is changed - (Check if) Task name is equal to [no value] - (Do this) Set task name to Deal name.

That might buy some time for the Deal name automation to finish, and update your no value name to the correct one.

Again, I’m not entirely sure this would work but it’s probably the first thing I would try. If it doesn’t work, there’s probably another trick I can figure out.

Welcome, @Joe_MacKenna,

In these circumstances, what works best is:

  1. Task added to project > Value custom fields and Move to Ready (or some other) section or group
  2. Task moved to Ready > Set task name

This separation ensures (1) is done before (2) starts.

Thanks,

Larry