Skip to main content

User guide for dynamic tables

How to use dynamic tables to manage variable data within a project?

Updated over 2 months ago

Glossary

Concept

Description

Objects

Database entries (e.g., products sold, stores, discounts, etc.) used in a dynamic table.

Smart fields

Properties that define objects (these do not appear in the list of existing smart fields).

Object instance

An entry or record in your table linked to an object.

Add a dynamic row

Add a dynamic row within a project.

Catalogs

Saved and reusable object instances.

Related fields

Link between objects (e.g., product → discount).

Definition

A dynamic table is a component that can be inserted into a contract template, allowing the management of a variable number of rows.

It is used when contractual information is not predetermined, such as in purchase contracts, service agreements, or software license sales.

Use cases covered

  • Purchases / commercial contracts: Lists of products or services purchased for stores

  • Service provision: A variable number of rows depending on the services sold

  • Sales / quotes: A variable number of rows depending on the products sold

Key concepts

Custom objects

Dynamic rows are built around custom objects.
An object can represent a product, a store, a service, etc.

Each row in the table is an instance of this object with its own properties.

Examples:

  • Object "Product" → Fields: name, price, quantity

  • Object "Store" → Fields: name, region, address

  • Object "Service" → Fields: type, frequency, price

Each dynamic table can only be linked to one object.
An object is reusable across different templates.
Using the same object in multiple projects allows data consolidation across negotiated projects on the platform.

Custom fields specific to the object

These custom fields are different from those in dynamic components. They cannot be used in views or filters.

They are the columns of the table, configured for the object.

Examples:

  • Text → Alphanumeric field

  • Number → Numeric field

  • Dropdown list → Single or multiple choice

  • Date → Date field

  • Relation → Field that references a value from another object

    • Example:
      If I have Table A for products and Table B for discounts, I can apply in Table B a discount to products listed in Table A.

Inserting dynamic rows in a table

A “Add a dynamic row” button allows users to add dynamic rows to tables within a template.

Configuration

In templates

  • Configuration is done only in the template for now (no dynamic row insertion directly within a project).
    → Display order depends on the order set in the template.

From projects

Once the project is generated from the template, users can:

  • Manually enter as many rows as needed in the dynamic table (only possible if no catalog is set for the table's object)

    • or import an Excel file to populate the dynamic table

  • Select instances from a predefined catalog (only possible if a catalog has been configured)

Catalog import

  • The import is done using Excel templates generated and downloadable from the interface.

  • The import columns must match the object’s properties.

  • Items can only be added to the catalog from the catalog itself, not from the project, for better data tracking.

Did this answer your question?