Forum Discussion
Strange behaviour between tables with relationships - returning row combinations that do not exist
- I have fixed this issue. I simply deleted all relationships and remade them. Most likely issue is that somewhere when setting up my relationships I have created something that was not correct and hadn't noticed. Since rebuilding all of the relationships it is behaving as expected. Classic PICNIC issue (Problem In Chair, Not In Computer)
So just to confirm, when you add the contract ID into the table it works as expected. If this is the case, this is because it needs the contract ID in there to complete the filterof propagation by the relationship.
Perhaps you're correct. But that is not required in my other scenarios where i recreated the set up with the two tables in question (see screeshow below):
In addition to that if i bring in a single value from contract e.g. just project_id and contract_no when using the problematic set up i get the correct values returned
If the problem was recreateable in other scenarios i'd perhaps understand but it isnt. Could this be connected to any of the Fabric outages? Is there perhaps a strange setting or quirk i've managed to turn on.
- I have fixed this issue. I simply deleted all relationships and remade them. Most likely issue is that somewhere when setting up my relationships I have created something that was not correct and hadn't noticed. Since rebuilding all of the relationships it is behaving as expected. Classic PICNIC issue (Problem In Chair, Not In Computer)