topic Re: Drawbacks of circular reference and Synthetic key in QlikView

Drawbacks of circular reference and Synthetic key

Mon, 03 Mar 2014 08:28:20 GMT

This is venugopal

I want to know only the Drawbacks of circular reference and Synthetic key?

why we have to avoid those?

If we keep what problems will come?

Thanks in Advance

Venu

Re: Drawbacks of circular reference and Synthetic key

Mon, 03 Mar 2014 09:27:42 GMT

Check this docs help ful to you.

Regards

Re: Drawbacks of circular reference and Synthetic key

er_mohit — Mon, 03 Mar 2014 09:43:27 GMT

Go to this link

Re: Drawbacks of circular reference and Synthetic key

amit_saini — Mon, 03 Mar 2014 09:45:48 GMT

Hi Venu,

In short:

Synthetic keys link tables that have more than one field in common. QV creates these keys automatically.

You need at least two tables in your data model.

Though you should carefully think about avoiding these keys, you might be able to live with them.

Circular loop means you have alternative paths between two tables, so you need at least three tables in your data model to run into this. QV can't live with circular loops, it will break the loop by loosely couple one of the tables automatically.

Thanks,

Re: Drawbacks of circular reference and Synthetic key

bimartingo — Fri, 30 Jan 2015 21:42:18 GMT

Thank you VERY MUCH!!

It's not only a very good introduction to this theme, but also a warning to those who thinks it's only a matter of simply loading data but, more than that, it can take a big effort and is crucial for the correct deploy of business data information through the Dashboards.

Thank you again,

M.G.

Re: Drawbacks of circular reference and Synthetic key

bimartingo — Fri, 06 Feb 2015 10:00:20 GMT

This presentation is great! But there are images, or at least it says it should have, that are not showing up. I only see a reminder at the images place stating that "can't show image at this moment" or "Powerpoint prevents you from open this image".

Regards,