How do I use datasheets across multiple entities?

If you run the same datasheet-based control across many entities - balance sheet reconciliations are the classic example - Entity Management lets you do it from a single control instead of one per entity. This article explains how entity-scoped datasheets work and how to set them up.

The problem this solves

Without entity scoping, a datasheet control had to be split into one control per unique grouping. For a balance sheet reconciliation that meant a separate control for Company 100 Fixed Assets, Company 300 Fixed Assets, and so on - hundreds of controls for a large group, each tied to one company-and-area combination.

How entity scoping works

The datasheet setup gains an entity column. The underlying data is exactly the same as before - but instead of grouping by company and area, you group by area once and let the entity column handle the split.

1. In the datasheet, make sure each row carries its entity (e.g. 100, 300). 
2. When you assign the grouping to a control, tie it to the area once — e.g. "Fixed Assets" — not "Fixed Assets Company 100", "Fixed Assets Company 300", and so on. 
3. Impero then distributes the rows automatically by entity: the Company 100 user sees only entity 100 rows, the Company 300 user sees only entity 300 rows.

The result is one control, scoped per entity automatically - far fewer controls to build and maintain.

Good to know

• The data and what each user ultimately sees are unchanged - you're just managing it through one control instead of many.
• This is one of the trickier parts of the module to set up. If you're scaling a datasheet across entities and something isn't behaving as expected, reach out to support.