Ambiguity validation not in place

[IvanS]

Hi team,

for the first time in my career, I have managed to set up 2 different paths to filter table without getting ambiguity error. Please find below screenshot from Model view (Layout). I was able to publish dataset without any issues but there was one side-effect of this change. The result of LOOKUPVALUE functions in Timesheet table was filterred by name of Driver in Fleet table. Which is strange as LOOKUPVALUE shall be independent from the relations between tables.

Is this bug or feature? I am using version December 2023.

Thank you for any clarification
IvanS

[Idrissshatila · Accepted solution]

hello @IvanS ,

I think this is normal in your data model because there is a two way filtering between the fleet table and users table which means that both tables can filter each others. so in your scenario table fleet is filtering users table and users table is filtering timesheet table.

the filtering is going like this fleet > users > timsheet.

to prevent this, you can make the filtering direction between fleet table and users table to single instead of both where the arrow is going from the users table towards the fleet.

[IvanS]

I mean, I understand that using one-way relationship will solve the issue. But previously I was getting error message that ambiguity is in place. Not sure why I did not get that message and was able to create such relationship.