This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
I think you can/should do away with the virtual column, and make Classification a real column.
Create an action for the Customers table of type Data: set the values of some columns in this row that recomputes the rowโs Classification column value.
Create an action for the Leads table of type Data: execute an action on a set of rows with a referenced table of Customers, a referenced rows of LIST([Customer]), a referenced action of the Customers table action in (2) above, and a condition expression that checks those two criteria you mention.
Attach that Leads table action from (3) to the Form Saved event action in whatever Leads table form users use to change the Stage column.
And/or attach the action from (3) to any other actions that modify the Leads table.
Alternatively, donโt do (4) and/or (5), but instead attach the action from (3) to a workflow that monitors for changes in Leads.
LinkedIn
Twitter
