Sometimes a formula will try to access an attribute that doesn’t exist:
When this happens, it can wreak havoc on a series of in doc variables by turning them all into error symbols.
Even attempts to manually override the behavior doesn’t fix the issue:
If(applicableManualResets.IsBlank(), false, [...] applicableManualReset.[Reset Time] [...])
Still results in a symbol because
applicableManualReset doesn’t have a [Reset Time] column right now, but it will once certain conditions are met (if Reset Time is > some value and < some other).
IfBlank can’t get around this with its current setup, but it could if it were given an additional argument allowing the user to specify what to do if the value is not blank.
E.g. in this case I could use it as:
applicableManualReset.IfBlank(false, [Reset Time])
Perhaps there is a way I could be structuring my formula differently to avoid this issue. If so, here is the full formula:
If(applicableManualResets.IsBlank(), false, applicableManualResets.FormulaMap(WithName(CurrentValue, applicableManualReset, [Oldest Epoch In Occupancy] <= applicableManualReset.[Reset Time] AND CurrentCount.Epoch >= applicableManualReset.[Reset Time])).Contains(True()) )
And here is a screenshot of the error in action: