We’ve been having a lot of success with using the content validator as part of our deployment pipeline, but recently ran into a use case which I’m not sure the content validator supports.
For any dashboard or look that utilizes a dimension as part of the filter predicate, I’d expect a rename to be picked up by the content validator. However, what if the dimension’s type changes? For those existing dashboards and looks, would it be expected that they would show up as having invalid filter values given the dimension’s new type?
We ran into an example of this when we changed a yesno type to a string to allow multiple values. All the existing filters were expecting “Yes”/“No” which were no longer valid after the dimension change.
If this is not an accepted use case, are there any shortcuts or workarounds that don’t involve iterating through all looks and dashboards and manually checking those values? Thanks!