At face value adding a property to an OrgVue dataset is straightforward, however there are increasing levels of functionality you can overlay as you build up your core knowledge over time as you feel more comfortable with OrgVue.
This article cross-references multiple other articles if you wish to research deeper still.
Basic Add/Edit/Delete Property Approach
These are the steps:
- if you wish to add a property, in Worksheet view in the dataset, access the menu bottom left, click on the >> icon to move to the property dialogue
- in the next screen, select Add Property
- choose a Key, Display name and appropriate Type, click on Add.
NOTE: DO NOT include in the property key either a full stop or a comma (the "." and "," characters).
- note, the key will be the reference point for all expressions and exported values, not the display name: the display name is for visualisation in OrgVue: in practice, for ease of use we recommend using the same property key and display name
- once you have added a property, that is now available to all nodes in the dataset
- if you wish to edit property contents, access the property via the bottom left menu as above, navigate to the property via the sub-menu as above (or use Find Property), click the cog icon visible next to the property label to access the previous dialogue in edit mode
- if you wish to delete the property, follow the same sequence again as Edit, choose Delete from bottom left on the Edit Property dialogue, select OK
Property Population with Expressions
- Typically property values are derived, not manually updated as would be required in the above example, using expressions (see Gizmo introduction here)
- An expression is added in the main edit box, above Aliases
- If the defaut settings are applied, adding an expression and Apply will show the value of the expression result in the property for all nodes in the dataset
for advanced users consider the impact of the following via the links shown:
- to ensure results are displayed properly, ensure that Type shown matches the expression: in the above instance it should be clear that True and False are the only possible outputs, so Yes/No may be a better choice of type than Text
- when an expression is performing some maths based function, ensure that property and all its dependents are set to type Number
- and that an appropriate number mask is applied
- when troubleshooting, if a numeric expression is returning a zero, the first thing to check would be that the property is a number field and not a text field.
... however if you import say $100,000 from Excel into OrgVue, that would be interpreted as text so any calculations on the property would not still apply. In this case the approach would be to have pure number format (i.e. 100000) in Excel and then apply any desired number formatting once the data is in OrgVue
There are several other related topics to property settings, these articles reference these other aspects in context not covered above: