Non-published nodes and properties
Less than to read
In GraphQL, non-published nodes or properties refer to data elements or entities that exist within the database but are not accessible or visible to users or applications querying the GraphQL schema.
- Non-published nodes refer to nodes that are not intended to be directly accessed or queried by users or applications. Non-published nodes can be internal nodes used in composite nodes, or other node operations. However, they are not part of the data accessible to users.
- Non-published properties indicate properties associated with nodes that are not meant to be exposed to users or applications interacting with X3. These properties can be used internally on nodes without being part of the visible GraphQL schema.
Setup a non-published node
- In the Node bindings function (GESANODEB), set the Published field to Yes or No.
- On the example below, the SalesOrderQuantityLine node is set as non-published in the GraphQL schema as its properties are already exposed in the main node SalesOrderLine through composite references:
Setup non-published properties
- In the Node bindings function (GESANODEB), select the properties to be hidden on the node.
- On the example below, the saleableProductLine is a technical property selected to be hidden on the note TaskProduct:
Note: Setting up non-published properties on a node is not available for collections, standalone references, computed properties and transient properties.