Hi team, We’re amending our LDM setup for the Users → Objectives → Key Results tables, as users need to report on both objectives and key results using User attributes. In our current model, the Users / Objectives relationship works well, but reporting is incorrect when using Users and Key results data together (as user data points to objective owner data). We need to report on both the Objective owner and the Key Result owner (as sometimes they differ) from the user table, but since both relationships eventually point to the Users dataset, we’re getting alternative path warnings. What we've tried: • Directly linking Key results and User table • Implementing a bridge dataset (

Key Result Ownership

) with

key_result_owner_id

→

Users.id

Can you please confirm which approach is best practice to avoid the warnings? Also in this case what is the best approach, • keeping the bridge dataset, or • creating a direct relationship from

KeyResults.owner_id

→

Users.id

? We want to ensure the model supports both ownership roles correctly without ambiguity or unnecessary duplication of the Users dataset. Thanks in advance for your guidance!

New message text here

Visually

Hi Raffaella, please note that with new implementations in your LDM our Services team can assist with modeling. The resources provided above can certainly assist with theory and logic but actual implementation of your LDM is a bit out of scope of our support team, whom deal with break/fix issues. For any further assistance, I would suggest to reach out to your Account Owner.

Hi Joseph, thanks for your response. We can close this ticket then.