The isIn column is used to import/export outgoing isIn relations between Definitions or Nodes.
This column works a bit like the Relation Column and the Assignment Column. The major difference is the absence of subcolumns, here you can only create outgoing b:isIn relations.
If you want to create an IsIn relation between Definitions, you must use the syntax in the Relation Column.
You can also remove relations.
In the example below, relations are defined with different syntaxes:
And you can also remove relations using the {clean} keyword.
IsIn |
Outgoing isIn relations |
slot:/Services/BtibService/aspectContainer/aspect/nodeDefinition |
$NodeDefinition1 |
$Aspect/nodeDefinition2 |
#NodeDefinition2;#Aspect/nodeDefinition3 |
{clean} |
Id
Variable
Relative slot path
Absolute slot path
If you want to create an IsIn relation between Nodes, you can use both the Relation Column and the Assignment Column syntaxes.
(If you are using a model path from the assignment column, you cannot use a relative path)
In the example below, relations are defined with different syntaxes:
IsIn |
Outgoing isIn relations |
slot:/Services/BtibService/aspectContainer/aspect/nodeDefinition/node |
$Node1 |
$NodeDefinition1/node1 |
#Node2;#NodeDefinition2/node3 |
Node/Node1/Node2/Node4 |
Id
Variable
Relative slot path
Absolute slot path
If the relative path goes all the way back to the station, we will encode the path using a lower priority encoding method (here an Absolute SlotPath) |
Here is an xlsx with the different examples and a basic BtibService:
BtibService.bog
defineIsInRelations.xlsx