Skip to content
Developerhome
Product homepage
X3

Non-generated properties

  Less than to read

Non-generated properties on nodes typically refers to those properties explicitly defined as non-generated on the node. This is opposed to properties that are automatically generated based on the table definition.

Distinguishing between these types of properties can be important for data management and querying nodes.

  • As an example, the SORDER table stores properties for both SalesOrder and OpenOrder nodes. Distinguishing properties exposed on each node ensures the integrity and accuracy of information stored on these nodes.
  • On the example below, the validityDate property defined on the SORDER table belongs to the OpenOrder node is not generated on the SalesOrder node. This is because the property is marked as Excluded for this node:

Reminder

  • If an unpublished node is a reference in another node, the reference property is also marked as unpublished in the second node.
  • If a key property is unpublished:
    • The node remains available for queries despite a key property not being published.
    • If the node is used as a reference in another node, it remains available as a reference.
  • If a key property is excluded, the entire node is not generated by the code generator in VS Code.