Currently i have a query that returns a bunch of log messages that I'm interested. For some of these messages, they have unique identifiers which means that when looking at the data in a matrix, each item takes up a separate row. To get around this, I have another query which has a mapping of strings with masks to the friendly message i want shown:
Pattern > NewMessage
"Time of day is: *" > "Time of day is: [TIME]"
"Product * was deleted" > "Time xxx was deleted"
...
To make this work, I have the property `Message` on the `ClientMessages` query that has the original content and a calculated property that has controls how the pattern is applied and returns the `NewMessage` based on the `Pattern` from the `_MessageOverride_` query. That query looks like the below:
MessageOverride =
VAR Matches =
CALCULATETABLE(
GENERATE(
ClientMessages,
FILTER(
_MessageOverride_,
SEARCH(
[Pattern],
[Message],
1,
0
)
>0)
)
)
VAR matchMessage = CONCATENATEX(
Matches,
[NewMessage],",")
RETURN IF(ISBLANK(matchMessage), [Message], matchMessage)
All the above works great, not a problem. The problems start when I try and do more "operations" based on this new `MessageOverride` column.
For instance, I have another table, which allows me to override the `Type` a given message has. This table looks like the below:
Message > NewType
"Time of day is: [TIME]" > Other
"Time xxx was deleted" > Crud
...
I went to setup a relationship between the `Message` column in this `_MessageTypeOverride_` query, to the new `MessageOverride` column from the above DAX query (so that I could have a new column based off it), but I end up getting the below circular dependency error. You will note that I want to be able to base the relationship off the result (i.e. "Time of day is: [TIME]") rather than the source (which has unique data in it).
> A circular dependency was detected: ClientMessages[MessageOverride], ClientMessages[TypeOverride], {GUID}, ClientMessages[MessageOverride]
TypeOverridden =
VAR FaultTypeRelated = RELATED(_MessageTypeOverride_[NewType])
RETURN IF(ISBLANK(FaultTypeRelated), ClientMessages[FaultType], FaultTypeRelated)
I tried setting up the same DAX query I have for the old messages to new messages to try and get around the problem, but I ended up getting the same issue.
I know from reading hear - https://www.sqlbi.com/articles/avoiding-circular-dependency-errors-in-dax/ - why I am getting the circular reference, but I don't know how to do what I need to do differently to avoid the issue.
Thoughts?
