Are single-select fields still limited to 500? I would like an easy way to associate a customer with a service or project. I originally wanted to use a single-select field as it can be selected easily at a form submission but we need more than 500. I tried to use form branching to provide different choices but was unable to link to the same custom field. I would love if there was a way to perform a vlookup of sorts by looking into an existing asana reference project with all of the customer details. This would allow it to automatically pull the name, address, contact number, etc when selecting a site.
I realize that creating a project per customer could pull that projects custom fields into the ticket which would be helpful, but I’m not clear how I could select the customer in the form intake process other than creating multiple custom fields (500 max each) that would then trigger a rule to multihome the task to an associated customer project. Way too many rules.
I’m considering using a portfolio instead of a reference project with common fields for the items we are tracking for our customer sites. Editing could be done at the portfolio or the project level. Nested portfolios could be used. Portfolio: Customer Type could contain Customer portfolios which would then contain customer sites.
The form would likely require manual typing of the customer name and site and then the intake process would include someone multihoming it to the correct site project.
Yes the current limit of options within a single-sleect or multi-select field is 500. Refer to this post for all limitations.
There, you will also find the limitation on Portfolios is 100 for the Advanced tier (currently unlimited for legacy Business tier, until it is phased out) but unlimited for Enterprise tiers. So portfolios may not be a scalable solution for you. Instead, you could use Teams (which are unlimited for all tiers) as containers for Customers, and instead have a CRM type project where each task is a customer.
Regarding the VLOOKUP that you mention, you may want to add your vote to my post here. This would be a really cool feature, but until then, you may perhaps be able to leverage Zapier’s Tables feature or lookup tool for something like that.
Thank you so much for both of those gems. Voted for both.
I will definitely rethink back into doing a CRM project due to the limitations with the hopes of a lookup option in the future.
Zapier table operations are now 0 actions which would make building and maintaining the table take 0 actions? Updating a task with all the lookup values may take only 1 action?
What would be the best method to get the customer key into the task for the zapier integration? Search CRM, copy/paste?
I am thinking the same Zap would be able to add a customer record to the CRM project if the key doesn’t match and all the other fields are filled out. Hoping that will also subsequently trigger the zapier table update. Now I need to look into Zapier table limitations and turnaround time.