Hi! As a newer user, I’ve gone through tons of content but I haven’t been able to achieve something that I would expect to be possible.
On the submission of a form which allows the submitter to select a US State, we would like the row that is create to be assign to a particular sales rep that is assigned to that state. IE, if someone makes a request for Texas, then an item is create and Bill, the Texas sales rep, gets assigned to that case.
@andrewalmand Thanks for the reply. The state data is in a drop-down, but that isn’t a requirement. I understand that Status isn’t an option because the max number of statuses is something less than 50.
Ideally, I’d like the rep to be assigned to the person column so that we can have the rest of the process worked in Monday.com
Okay good that is how I figured it was set up, and makes the most sense. Yes currently Status columns are limited to 40 items so
I’ve figured it out, sort of…
It will require that you install an App from the Monday.com App Marketplace. General Caster is honestly the most useful app on the marketplace and really opens up so much in the way of bypassing formula and column type compatibility issues. Instead of performing formulas in the Formula column, General Caster does it outside of Monday and then cast the result to basic columns like text, numbers etc. General Caster is here. Get rid of formula columns! - #11 by rob
Now for the specifics and the roadblock i’ve hit. It’s just a SWITCH formula in the General Caster which I’ve successfully created. See below example:
This formula will check for the state in the dropdown column and then produce the corresponding ID number for the rep. So in the above example, when FL is picked it should cast the ID# 10955951 which is my User ID in Monday. If TX is picked then it cast the other ID#. The issue is that it won’t cast that number to the Person column.
But If I have that number placed in a Text column and I tell General Caster to cast it to a Person Column it works!
But for some reason it won’t if the ID# is the result of the formula. A workaround would be for one General Caster formula to send the result to a plain Text column, and the another to send the ID# to a Person column. I tested this and got it work only once. The formulas process at the same time and the first one rarely processes fast enough for the second one to use the result.
Bringing in @rob from General Caster here to see if he can help further. Maybe it’s just a matter of formatting the result of the formula so it can properly cast it to the Person column.
Thanks, Andrew, this is super helpful. General Caster is great to know about. Although that workaround might work, perhaps @rob will manage to work directly from a formula at some point. Thanks again for this useful and thorough reply.
