Usage of USERELATIONSHIP function

[Anonymous]

We use a report that makes a reference (via active table relationship) to a specific table. It is necessary to deactivate this relationship to properly calculate a value in a visual.  However, when I deactivate this relationship it causes MANY (near 100) other items to break.  I am able to apply formula fixes to these "broken" visuals by using the USERELATIONSHIP function. 

My question is "In place of changing formulas in many places, Is there an ANTI version (or usage) of USERELATIONSHIP that I only apply in one location to apply a fix to a single visual). Can I maintain the inplace table relationship and have the visual ignore it?

I've tried to create a table that includes the matching date values that are related and that does mitigate my issue.

Additionally, this project has patient health information and I wouldn't be able to share a version of the file.

[AlexisOlson]

Can you explain how deactivating the relationship makes the visual work properly, i.e., what changes in the filtering?

I'd guess you could write measures for the visual that behave similarly to severing the relationship.

[Anonymous]

Thanks for your replay, how do you write a measure that "severs"a relationship?

[AlexisOlson]

It's hard to say without knowing the context. Can you give an example of a measure you are using in a visual and how it behaves differently with and without the relationship?