All-
FTC recently updated to V14.1 and I am noticing relative dates are no longer an option for Output Set parameters.
In previous versions the text input allowed Orgs to put in parameters such as "DayRunDate +1" or "RunDate", unfortunately it seems the new output set builder does not like this and rejects even saving previous versions of output sets that were present from past versions.
Right now the only work around I have found is replacing these parameter values with valid SQL values such as DateAdd(dd,1,Convert(varchar,GetDate(),112)) in the TX_QUERY_ELEMENT_VALUES table manually.
Has anyone had to find/found a better work around so far for V14.1?
Chris
Christopher -
Thanks for the workaround. I found I had to use cast(DateAdd(DAY,1,GetDate()) as date) to avoid conversion errors.
Clarke
Since we have completed the work for relative date filters to be used with Output Set Parameters in our v15 development environment, we are working on releasing it as soon as possible, rather than holding off until v15. We anticipate it being part of the next v14.1 Service Pack, v14.1.3, which is expected to be be released at the beginning of May.
Sweet!
Karen, did this fix get into that service pack? I skimmed the release notes but did not see it.
Hi Clarke, yes this did get added to the 14.1.3 Service Pack that was released yesterday with the following release note: Relative date options are now available when configuring my Output Element Filters
The full release notes for this Service Pack can be found here: www.tessituranetwork.com/.../v14-1_SP
We have loaded service pack 14.1.3 in our Test environment, and were delighted to find relative dates available in the Output Sets. But...
The way our marketing department uses output sets selects information within a date range, like between (DayRunDate +1) and (DayRunDate +8). It looks like relative dates are not available when you use the "between" operator. Is there a way around this? I tried having 2 separate elements pointing to the same data with separate >= and <= statements, and that looks like it failed spectacularly.