I have tables which are totally connected via inactive relationships which are all of a sudden causing visuals errors saying a relationship does not exist. But when I check, it does exists it just isn't active. This never used to be a probe
This issue has been confirmed as a known issue internally and will be fixed next month. See workaround below.
1) Users need to change their measure definition. Example : from Calculate(…, UseRelationship(…)) to Calculate(…, UseRelationship(…), CrossFilter(…))
2) Can add CROSSFILTER() on the same relationship to the offending measure to restore the old one-way filtering behavior
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.