topic Re: How to avoid Circular loop or synthetic key in QlikView

How to avoid Circular loop or synthetic key

vengadeshpalani — Wed, 25 Nov 2020 16:16:04 GMT

Re: How to avoid Circular loop or synthetic key

swuehl — Mon, 03 Jul 2017 19:32:21 GMT

Maybe just create two separate master calendar for your two dates.

Why You sometimes should Load a Master Table several times

You could also consider creating a single fact table, maybe by mapping the crew statuts where crew status date equals job status date. Well, here starts wild guessing, since you need to decide how you want to model your data, and that can only be answered if all report requirements in combination with the base data model are taken into account.

Re: How to avoid Circular loop or synthetic key

MK_QSL — Mon, 03 Jul 2017 19:33:56 GMT

Concatenate two tables like below

JobInfo:

LOAD JobID,

JobStatus,

JobStatusDate ,

Crew

FROM [Test.xlsx] (ooxml, embedded labels, table is Sheet1);

Concatenate

CrewInfo:

LOAD Crew,

CrewStatus,

CrewStatusDate

FROM [Test.xlsx] (ooxml, embedded labels, table is Sheet2);

Now use Canonical Calendar as below.

Canonical Date

Re: How to avoid Circular loop or synthetic key

vengadeshpalani — Mon, 03 Jul 2017 21:51:58 GMT

when i was select crew it affect two tables

but when i select job no it does not associated

when select 4 its crew is c, it wants to show all crew status but it has not shown what I did wrong

Re: How to avoid Circular loop or synthetic key

arvind_patil — Tue, 04 Jul 2017 06:10:38 GMT

Hi Vengadesh,

If data is same granularity then concatenate it.or else use the link table.

Thanks,

Arvind Patil

Re: How to avoid Circular loop or synthetic key

swuehl — Tue, 04 Jul 2017 07:10:37 GMT

When you select a column that is not filled with values for each record, you automatically remove the records with NULL from your current record set. For example, selecting a JobID will remove the crew status information.

That's due to your data model, concatenating the given two fact tables.

You may work around this using set analysis in certain use case scenarios, but as I said, it's hard to help here with the context provided.