Yes you can include the parameter as a constant column, and the logic of your approach seems ok (I can't test it right now). Maybe try something like this?[left]
SELECT
@SELECT:DIM:USER_DEF:IMPLIED:INVESTMENT:V.UNIQUE_ID:UNIQUE_ID@
, @SELECT:DIM_PROP:USER_DEF:IMPLIED:INVESTMENT:V.PROJECT:PROJECT@
, @SELECT:DIM_PROP:USER_DEF:IMPLIED:INVESTMENT:V.WEEK_ENDING:WEEK_ENDING@
, @SELECT:DIM_PROP:USER_DEF:IMPLIED:INVESTMENT:V.FILTER_VALUE_FROM:FILTER_VALUE_FROM@
, @SELECT:DIM_PROP:USER_DEF:IMPLIED:INVESTMENT:V.FILTER_VALUE_TO:FILTER_VALUE_TO@
FROM (
SELECT
S.ID UNIQUE_ID /* you may not need to do this concatenation, now its numeric */
, I.NAME PROJECT
, S.WEEK_ENDING WEEK_ENDING
, @WHERE:PARAM:USER_DEF:DATE:WEEK_ENDING_FROM@ FILTER_VALUE_FROM
, @WHERE:PARAM:USER_DEF:DATE:WEEK_ENDING_TO@ FILTER_VALUE_TO
FROM INV_INVESTMENTS I
JOIN ODF_CA_STATUS S ON I.ID = S.ODF_PARENT_ID
WHERE S.WEEK_ENDING >= @WHERE:PARAM:USER_DEF:DATE:WEEK_ENDING_FROM@
AND S.WEEK_ENDING no guarantee on this code whatsoever! [left] [left] nag nag, I prefer commas first ;-) see
this image for why.[left]
[left]