Qlik Community

New to QlikView

Discussion board where members can get started with QlikView.

Announcements

Breathe easy -- you now have more time to plan your next steps with Qlik!
QlikView 11.2 Extended Support is now valid through December 31, 2020. Click here for more information.

Not applicable

Architecture to avoid loops

Hello,

I am facing the following problem (see attached diagram).

I have 2 systems (SysA and SysB) with some databases (SQL and MySQL).

Both have tables related to users and projects.

Both contain different information (ie one table has the user name while the other has its telefon number) and I would like to aggregate that.

I already 'joined' the projects tables using the AS keyword to rename the key in both project tales.

Now I would like to do the same with the users but it creates loops.

What is the best approch to handle this?

2 Replies
hallquist_nate
Contributor III

Re: Architecture to avoid loops

Whenever I have an association challenge like this, I turn to the Link Table model.  It has yet to fail me in the most complex association situations.

Not applicable

Re: Architecture to avoid loops

Can you point me to the documentation on the Link table model?