Use case: picklist change
Renaming a stage or retiring a value ripples through Flows, validation rules, Apex and reports. See all of it, and the records involved, before you change anything.
In one paragraph
Changing a picklist safely with SyncOnAI 360 means listing the Flows, validation rules, Apex and components that reference the field, counting live how many records hold each value, drafting the change, and shipping it as a proposal with named checks, validation against the org and approval, with rollback for the metadata.
01The problem
Picklist values are compared as text all over an org. Change one, and a Flow decision, a validation rule or a line of Apex quietly stops matching.
Values are hardcoded in automation, rules and code.
Old values stay on records after the picklist changes.
Downstream consumers expect the old values.
Sales stages change exactly when the pipeline matters most.
02refs
Ask what uses the field, or open it in Lineage, and see the Flows, validation rules, Apex and components that reference it, from an evidence-based dependency graph. Where source could not be read, the answer says so.
Open each referencing Flow in the Flow builder to see, in plain sentences, how it uses the value.
03records
Ask for a count of records by value and the query runs live against the org. Retiring a value used by thousands of open records is a different decision from retiring one nobody chose.
04change
Draft the change and update the references, in the builders or through the chat, as one set of proposals. Each carries named checks, its blast radius and a validation against the org before approval.
Freeze windows in the deploy policy can stop changes landing at quarter end, and every deploy leaves a receipt with rollback for the metadata.
05data
Rollback restores metadata, not data, so plan how existing records will be handled before the change ships. Anything that would update records from the chat waits for a person to press Allow.
06verify
Components deployed through SyncOnAI 360 are read back straight after a successful deploy, so lineage reflects the change at once. Ask again what references the old value: anything still listed was missed and can be fixed before users find it.
Run the audit again to check that no new overlapping automation or broken references appeared.
07rules
Any validation rule or Flow decision that compares the field to the old value needs the new value too, or it will stop matching. Open each referencing Flow to see its decisions in plain sentences, and ask the chat to draft the matching updates as proposals alongside the picklist change.
Shipping the references and the picklist together means there is no window in which automation runs against values that no longer exist.
08How it works
References, records, change, release.
List everything that uses the field.
See how many records hold each value.
Decide on existing records and update references.
Propose, validate and approve outside freeze windows.
09Checklist
10Before and after
Without
With SyncOnAI 360
Change the value and wait
Every reference listed first
Records left with old values
Counts per value, live
Flows silently stop matching
References updated in the same change set
Changed at quarter end
Freeze windows enforced
12Questions
It lists Apex that references the field from parsed source; open each class to see how it uses the value.
Yes, live against the org.
Anything that changes data waits for a person to press Allow, and rollback cannot reverse it.
Yes, with freeze windows in the deploy policy.
Record types and value sets are synced metadata; the dependency answer states what was examined.
Yes, against the target org, before anyone approves it.
The metadata, yes, from the receipt. Data changes cannot be rolled back.
Yes. Every plan includes every feature.
It lists the Flows that reference the field, and the Flow builder explains each one's decisions in plain sentences.
Yes. Members can deploy to sandboxes freely, so test the picklist and its references there first.
13Keep exploring
Connect your Salesforce org. Run your first health scan. Ask your first question. See what you've been missing.