Many of us hit Save every day… but have you ever thought about what happens behind the scenes? ๐
Simply put, here’s the journey:
- ๐ข 1. JavaScript (OnSave) – the first thing that runs if you have JavaScript on the form.
- ๐ข 2. Business Rules – any Business Rules tied to the data get executed.
- ๐ข 3. Pre-Validation Plugin – this is the first plugin stage, usually used to validate data before any save operation.
- ๐ข 4. Security Check – the system makes sure the user has permission to save.
- ๐ข 5. Pre-Operation Plugin – your last chance to modify the data before it’s written to Dataverse.
- ๐ข 6. Save to Dataverse – this is where the data actually gets saved.
- ๐ข 7. Post-Operation Plugin – after saving, you can run additional operations or link the data to other entities.
- ๐ข 8. Power Automate / Workflows – if there are any Flows or Workflows, they start running based on their configuration.
- ๐ก Why does this order matter?
Because it helps you know: what changed after the save, when to use a Plugin versus JavaScript, and how to get to the problem faster when debugging.
- ๐ฏ The better you understand the Save journey… the stronger the solutions you’ll write, and the more time you’ll save when solving problems.