When a user edits data inside an embedded app and then tries to navigate away, Salesforce shows its standard unsaved-changes warning. It’s the same prompt users see on native Salesforce pages. Your embedded app tells Salesforce when it has unsaved work, and the platform handles the confirmation prompt.
From inside the embedded app (the guest), you use the view SDK to mark the view as dirty when the user makes an unsaved change, and to clear that state when the user saves. Salesforce re-bubbles this state to the platform navigation guard, which shows the standard confirmation when the user navigates away. Your app doesn’t manage the browser’s beforeunload event. The platform does that.
lightning-ui-embedding and loads successfully.Dirty-state tracking isn’t supported in the Salesforce mobile app.
Note
1import "@salesforce/platform-sdk/ui-embedding";
2import { createViewSDK } from "@salesforce/platform-sdk/view";
3
4const viewSdk = await createViewSDK();1await viewSdk.markDirtyState?.("profileForm");1await viewSdk.clearDirtyState?.("profileForm");The label argument identifies a specific region of unsaved work, so you can track more than one independently.
On an embedding surface, markDirtyState and clearDirtyState are always available. Off an embedding surface, createViewSDK resolves to an empty object and these methods are undefined. Guard every call with optional chaining, as shown with viewSdk.markDirtyState?.(...), so your app works predictably across surfaces.
Note
The unsaved-changes confirmation doesn’t appear when a user closes an embedded app that’s inside a modal by clicking the modal’s close (X) button. Dismissing a modal isn’t a navigation, so the platform navigation guard doesn’t run. If your app runs inside a modal, implement your own confirm-on-close.
j