-
Selecting and mapping relationship fields
Relationship pairs are handled automatically, but display fields must be chosen explicitly When a relationship field is exposed: The reverse relationship is included automatically.…
-
Remapping fields in modules
Keep module connections stable when databases or interfaces change You need to remap fields when the connection between a module and a target database can no longer rely on the previous field…
-
Mapping fields in modules
Remap source and target fields to the same interface fields to keep connections stable as databases evolve Field mapping lets module consumers connect a target database to a module and align incoming…
-
Relationship fields show IDs by default
Expose additional fields to make related records readable in target databases After a relationship field is connected, it initially appears in external tables as record IDs only in the target…
-
Relationship fields in modules
Share links between records while keeping relationships consistent across connected modules Relationship fields can be shared in modules through interfaces.…
-
Image fields and calculated fields in modules
Image fields can't be shared, and they can block exposing or updating formulas that depend on them ℹ️ Note: Image fields aren't supported in modules. Because of this:…
-
Selecting dependencies when calculations reference tables
Choose a meaningful display field when a formula depends on a table, not just a single field If a calculated field in a module depends on a table (rather than a single field),…
-
Selecting dependencies for calculated fields
Expose everything a calculation needs so it can be evaluated correctly in the target database When a module provider exposes a calculated field in a module,…
-
Calculated fields in modules
Share logic across modules by exposing computed fields that update automatically in target databases Ninox supports sharing calculated fields in modules.…
-
Dynamic Reports - Data from Different tables
Another question: Is it possible to call data from two different unrelated tables to fill the report? Like this: let xFilter := record(Reports,1).Filter; let x :…
