Occurrence Calculated Attributes
- Brok Howard
- Marianne Gjøviken
To create composite text attributes, you need superuser access to the database, as the setup is done in the Administration settings. Please refer to https://drofus.atlassian.net/wiki/spaces/DV/pages/1332416587.
Occurrence True/False and Value Example
Example:
Confirm the following two conditions before consider moving the occurrence forward into procurement:
If the product has a:
Document attached.
Unit price
Since we are working with an occurrence, we know that a room and an item have been defined. This example is checking across several modules at once. Two fields were added: Has document (yes/no) and Unit price.
The first part is an if/then format that checks if the product has a document AND has a unit price greater than zero. If both are true, we return TRUE. If either is not valid, we return FALSE. The Data type is a Yes/No, so in the occurrence properties panel, we will see a check box under Product Documents Status within a new group called Validation Check. This could also be a column added to an occurrence list to quickly see which occurrences are ready for procurement or used in a report filter.
The most powerful feature of calculated attributes with occurrences is that you can access all room properties, room data fields, item properties, item data fields, product properties, product data fields, occurrence properties, occurrence data fields, documents, and image fields. We can’t wait to see what you uncover as you leverage this powerful feature.