Hi team, hopefully easy issue. I am creating a custom record which will use a status, however 'next step' statuses should be restricted by the current status (eg if currently Pending, can only be changed to In Progress, not Complete). In an ideal world I'd run this via buttons & scripts however I am hoping to make this work on mobile as well which introduces some wrinkles. I've created a secondary custom record for the status and used a Multiple Select field to set what should be the 'next available statuses' options. Is it possible via Filtering & Sourcing to only show in the dropdown on the main custom record, statuses which are selected as next statuses, for the current status?

@cweier This will be tough with native sourcing & filtering as it would create somewhat of a "circular" logic when the filtering is based on the status field, but the status field itself is filtered by the criteria of itself. Ideally a workflow with buttons would be the best bet. What is your reasoning for not using the workflow buttons? They do work on most mobile browsers and even in the Netsuite mobile app.

@MGBC totally get the issues with it, was hoping somebody smarter than me had encountered the problem and come up with something already 🙂 I've been doing most of my button development with scripts not workflows, which seem to not show in the iOS app at least, so I'd just assumed you couldn't get buttons in the app. I'll do some more investigation - thanks!

use 2 status fields, one that is filtered and that a user can select. And the other hidden and can be used for sourcing and filtering

^^ This is the way.

Yes 2 fields could work possibly Field 1 - current status. Add a script or workflow to set this value before submit or after submit to the value of Field 2 when the record is saved Field 2 - status select. Add sourcing/filtering of “current status value from custom record” = current status on current record

Very late response but this has worked incredible, thank you all so much!