...
Unique data
The occurrence data within a room is always unique to the a specific FFE item in a room and is not inherited derived from the template (the template cannot have occurrence data). This means that even though two rooms have the same equipment list from a room template they can have different values between the each individual occurrence in each room (e.g. color or number).
There are numerous use cases where this can be utilized, but there is always a trade of between choosing to storing data on the occurrence vs. storing it on the Item (type). You can use occurrence data to allow for small variances that should not affect the room templates or in cases where there is a property more related to "where" than "how". E.g. color should vary depending on floor level, but the quantity of each type should be the same. If you use occurrence data you cannot use templates to save you from updating each record.
When changing multiple occurrences you can also update custom occurrence data, but note that it would only allow you to change properties that are available on all the occurrences.
See admin guide for how to create new properties (dynamic GUI) and how to control on what Item the property is shown (Item view filter). In other words, occurrence data cannot be inherited from the template itself. This implies that even if two rooms share the same item list based on a room template, the individual occurrences in each room can possess different values, such as color or quantity.
There are various scenarios where this uniqueness can be advantageous, although it requires a trade-off between storing data at the occurrence level versus storing it at the item (type) level. Occurrence data can be employed to accommodate minor variations that should not impact the room templates, or when a property is more relevant to the "where" aspect rather than the "how" aspect. For instance, the color of an item may vary depending on the floor level, while the quantity of each item type remains the same. If occurrence data is utilized, relying on templates to update each record becomes unfeasible.
Standard data:
Data that can be stored at the Occurrence level includes:
...
Serial Number - This running number is part of the https://drofus.atlassian.net/wiki/spaces/DV/pages/2487418939/Classification+and+Numbering#System-numbering solution that is combined with Number to define a unique Number per occurrence.
Number - The unique number per occurrence that combined the Item number with the Serial Number.
Name - Optional text to define a unique occurrence by name.
Quantity - how many times is the Items to be included in the room. The row of Item types would be a single Occurrence with a quantity of instances of that type.
Existing Quantity - If any of the Item types already exists so that procurement is not necessary, this can be specified here. This quantity will then be deducted from the net accounts for this Item.
Owner - If one or more parties own the Item Occurrence, the party to be specified as Owner of the Item Occurrence can be defined here.
Priority - Priority for how important the Item Occurrence is compared to other item Occurrences in other Rooms.
Comment - comments for the specific occurrence
Product - the linked products associated with the occurrence
Room - the linked room where the occurrence is located (when room based)
Responsibility - the responsibility of the item is carried to the occurrence by default. The occurrence can be overwritten with different responsibilities to further define specific responsibilities for the occurrence.
Item - the linked item associated with the occurrence.
Occurrence Data - Project defined data fields. See next section
The quantity of each Item forms the basis for the gross quantity of this Item in the room. The net quantity is the quantity minus the existing quantity. In addition, there are sub Item which are not to be included in the quantity calculation and deducted so that they are not part of the net quantity. Net quantity together with the Item budget price provides an estimate of how much an Item list for a room will cost. This total figure will be presented in budget reports and reports on Item in room.
Add additional properties
In addition to "core" properties it is possible to create project specific occurrence properties. This can be anything from numbers needed in the project to the color of a chair.
For detailed instructions on creating new properties using a User Interface Editor and controlling which item the property is displayed on (Item view filter), look at the admin guide User Interface Editor
Updating Occurrences data
When modifying multiple occurrences, it is possible to update custom occurrence data. However, it is important to note that only properties common to all occurrences can be changed.