In Perfect Doc Studio, you can create Nested Dynamic Tables by establishing relationships between two entities in the variables section. This setup allows the variables of one entity to be linked with those of another, enabling tables to dynamically expand based on their data relationships.
Example: If a Customer entity is related to an Orders entity, each customer’s table will automatically display all their related orders, adding new columns or rows as needed.
So, a Nested Dynamic Table represents a logical relationship between variables, where one entity acts as the parent and the other as the child:
Parent Entity: The main dataset driving the table (e.g., Customer).
Child Entity: The related dataset that expands dynamically based on the parent (e.g., Orders).
Has One – Used when one record from the parent entity is linked to only one record in the related entity
Example: A Customer has one Address, each customer is connected to a single address record.
Has Many – Used when one record from the parent entity is linked to multiple records in the related entity
Example: A Customer has many Orders, each customer can have several related order records.
Order.Name variable.Scenarios Where Nested Dynamic Tables Are Useful:
Nested dynamic tables are ideal for situations where a parent entity has multiple related child records. For instance, they can be used to generate customer statements with all transactions, insurance policies showing multiple coverages and claims, vendor catalogs listing all products, or employee performance reports with monthly metrics. This approach saves time and ensures documents are accurate, organized, and fully data-driven.