What Is FormSync?

FormSync Explained

ERP work is rarely confined to one screen. A planner looking at an item wants the item record, current inventory, open orders, and the bill of material visible together. FormSync makes that possible by establishing a parent and child relationship between open forms and passing the current record's key from the driving form to the followers. Navigate to a different item in the parent and every synchronized form refreshes to that item without the user re-entering the number.

Configuration is metadata rather than code. A synchronization definition names the participating forms and maps the properties that carry the context - typically the primary key or a filtering property. Once defined, the behavior applies wherever those forms are opened together, and it can be delivered as part of a role-specific workspace so users receive the arrangement rather than assembling it themselves each morning.

The productivity effect is easy to underestimate until you watch someone work without it. Re-keying an order number into three forms takes a few seconds; done fifty times a day across a customer service team, it is a meaningful share of a headcount, plus the transcription errors that come with manual re-entry. FormSync removes both, which is why it appears so often in well-designed SyteLine role workspaces.

Practical caution: synchronized forms all re-query when the context changes, so linking a heavyweight form into a frequently navigated arrangement can make the whole workspace feel sluggish. Keep synchronized sets small and favour lightweight views for the follower forms. If users complain that navigation stutters, look first at how many forms are syncing and how expensive each of their queries is.