There was a similar issue posted last year but I don't think there was a solution to it. Here is the issue:
We have an attribute qualification filter that uses custom between statement with an embedded value prompt:
ApplySimple("year(date(#0) - 2 MONTHS)*100+month(date(#0) - 2 MONTHS)",? [Enter a Value(Date).])
AND
ApplySimple("year(date(#0))*100+month(date(#0))",? [Enter a Value(Date).])
The value prompt has a default value of '12/31/2004'.
We are looking in to removing the value prompt and replacing it with a custom attribute that gets a max (date) from a table. So now, the logic should be:
ApplySimple("year(date(#0) - 2 MONTHS)*100+month(date(#0) - 2 MONTHS)",CustomAttriubte@ID)
AND
ApplySimple("year(date('12/31/2004'))*100+month(date('12/31/2004'))",CustomAttriubte@ID)
The attribute definition is where we are having issues.
It validates ApplySimple("Max(#0)", DT_ID), but the resulting filter fails once it is ran against the DW table because it places a column functin in the where clause.
Any other solutions out there?
Thanks in advance
We have an attribute qualification filter that uses custom between statement with an embedded value prompt:
ApplySimple("year(date(#0) - 2 MONTHS)*100+month(date(#0) - 2 MONTHS)",? [Enter a Value(Date).])
AND
ApplySimple("year(date(#0))*100+month(date(#0))",? [Enter a Value(Date).])
The value prompt has a default value of '12/31/2004'.
We are looking in to removing the value prompt and replacing it with a custom attribute that gets a max (date) from a table. So now, the logic should be:
ApplySimple("year(date(#0) - 2 MONTHS)*100+month(date(#0) - 2 MONTHS)",CustomAttriubte@ID)
AND
ApplySimple("year(date('12/31/2004'))*100+month(date('12/31/2004'))",CustomAttriubte@ID)
The attribute definition is where we are having issues.
It validates ApplySimple("Max(#0)", DT_ID), but the resulting filter fails once it is ran against the DW table because it places a column functin in the where clause.
Any other solutions out there?
Thanks in advance