how to handle in filters common date fields which must have different names?

[ioannagr]

Consider the following tables connected by unit:

Table 1:

[id control 1],

unit,

[date id control 1];

Table 2:

[id control 2],

unit,

[date id control 2];

Table 3:

[id control 3],

unit,

[date id control 3];

I made a dates table from the table all three come from . I linked them via unit again so that my filter selection become easier and to have one common date field for all control types:

dates table:

date as controldate,

unit ;

Also on it i built a master calendar to work on some cytd-lytd measures which of course come off wrong.

Any suggestions on how i should handle this date problem

without getting synthetic keys??

[marcus_sommer]

A quite easy approach would be to load all 3 table into a single-table by unifying the fieldnames and adding an extra field "Source" to be able to differentiate between the sources through selections or set analysis.

- Marcus