Enterprise automation often crosses systems with different record identifiers and response shapes. A Salesforce account ID is not a Dataverse row ID, even when both records describe the same customer. Use the approved mapping and patch only the fields the owner asked you to change.
The local designer models Salesforce Get records and Update record, plus Microsoft Dataverse List rows and Update a row. Reads expose a records array for Salesforce and a value array for Dataverse. Updates use the record's stable ID and preserve other fields. Your hidden event changes names, owners and row counts, so a copied literal cannot replace dynamic content.
These fixtures do not sign in to either service. Live permissions, licensing, pagination and production schema choices still need verification in the destination environment.
Connector response envelopes differ. Read the documented array, use the stable destination identifier for updates and preserve fields outside the approved patch. These actions use local rows rather than a signed-in enterprise account.