Filters and views can only be built upon contacts, categories, relationships, dates and tags, not upon calculation fields - at least not with strings. To my knowledge there are two roads:
- create a new calculation field with the same logic, but not with a text output but a number output (you can't convert the existing calc field, that's why you need to make a new one). I usually do it like that: 0 if inactive, 1 if active. Then you can filter for items where this calc field has a value greater than 1 or smaller than one. Since you only have two states (active and inactive) this could do it for you. You can't however make a view with sub-views "inactive" and "active", you can only make one view for active items and one for inactive.
- create a category field with "active" and "inactive". Then, create a GlobiFlow where you use your calculation field (string or number, doesn't matter) as filter for the action "update item" and let GF set the respective status with the category field. Actually you might need two flows, one upon "create item" and one upon "update item".
You might think that road 2 is just perfect. But there's one possible obstacle: if the calculation field is the only thing that changes, this won't trigger a GlobiFlow. Changes you make in related apps leading to a change in your calculation field will do just that but not fire a trigger. In that case you'd need a third GlobiFlow in the related app which, upon editing the field influencing your calculation, triggers the flow updating your category.
Comment actions
