Thanks for chiming in. I’m not sure your response quite clarifies for me when I should use ExactDimensionTimedValue – however, I’ve recently learned something new about the purpose of ExactDimension. And perhaps this will help with the type of answer I’m looking for.
It was explained to me that if I am storing a value of say, “inventory level”, I could store the value as an INTEGER. Or, I could store the value in an ExactDimension type.
The difference is as follows:
Say we’re dealing with eggs… with INTEGER, we could store the value (e.g. 12) and always use it at face value without knowing the unit of measure.
However, if we store the value as ExactDimension type, we could store it as 12 as follows:
In other data sets, perhaps quantities are counted as per “dozen”. We might then store the value as follows:
By the way, for those reading, you can find out all the supported Units by doing
c3Grid(Unit.fetch()). Notice that the multiplier of “dozen” is 12 “single”
So the BENEFIT of using ExactDimension is that, if we choose to store the data with Unit of Measure, we can have the platform convert between units of measure for us… and provide answers back with unit of measure (e.g. How many dozens of eggs do we have?). The platform, when aggregating across types that use different units of measure, can automatically compensate/convert between different stored values of Exact Dimension to give correct results.
So, using the above as an example explanation – it would be very helpful if you/someone could provide a concrete use case for ExactDimensionTimedValue.