Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi All!
I've managed to clean this up from 3 synthetic keys down to one. Please see the attached image.
Maybe this is a common problem, but I'm having trouble joining each table to the master calendar without creating a synthetic key. I am wondering if I should be using a single link table, but I've not had much luck creating one successfully and still have everything in my app continue to work.
Something that is possibly complicating things is several of the databases have fields that are the actually same thing (like facility location on the image) but labeled something else in their own databases, so they require a mapping table and renaming of the fields.
Hi,
the tables you link with [Master Calendar] should not contain any of the fields of the [Master Calendar] except the one field that links them together: [Period]
So after the linking:
Concatenate ([Link Table])
LOAD Distinct
Year,
Period,
[Year - Month] as [Month (#)],
Month,
Quarter
Resident [Master Calendar];
there should be the code to remove the other fields that are in [Link Table]
DROP Fields
Year,
[Month (#)],
Month,
Quarter
From [Link Table];
R.
Thanks for the reply. I'm still not quite sure I understand.