Hey Ivan,
I've been implementing something similar for a client this week. Here's what I've done:
Create a second form for the table, which contains just the fields you need to identify the Opportunity and the "lost reason" field you want to require. On this form, make the "lost reason" field required.
Change your button from running automations to displaying the current record on the new form in edit mode.
Then create an automation to kick off your processes for a lost opportunity, but trigger it based on the Opportunity record being edited and the "lost reason" field being filled in.
Happy to help more getting this set up during Data Collaborative's free office hours!
DC Office Hours Sign-up
| Quickbase |
remove preview |
|
| DC Office Hours Sign-up |
| When you bring additional fields into a conversion, Quick Base often finds inconsistencies. For example, say you're converting your Companies column into its own table. One company, Acme Corporation, has offices in New York, Dallas and Portland. So, when you add the City column to the conversion, Quick Base finds three different locations for Acme. |
| View this on Quickbase > |
|
|
------------------------------
Sam Jones
------------------------------
