V14.1 Output Sets, loss of relative dates for Output Set Parameters?

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

Parents
  • Hi Clarke


    The Between operator has never been available when using relative dates in List criteria or with flexible parameters in Output Sets.


    However, adding 2 filters (previous known as Parameters) to your output element will do the job 

    Example:

    perf_dt >= DayRunDate +1

    perf_dt <= DayRunDate +8


    This will behave in the same manner as using Between.

    Hope that helps
    Regards
    Sandra


Reply
  • Hi Clarke


    The Between operator has never been available when using relative dates in List criteria or with flexible parameters in Output Sets.


    However, adding 2 filters (previous known as Parameters) to your output element will do the job 

    Example:

    perf_dt >= DayRunDate +1

    perf_dt <= DayRunDate +8


    This will behave in the same manner as using Between.

    Hope that helps
    Regards
    Sandra


Children
  • Sandra!

      Thanks for the response.  There were a bunch of Output Sets here that used relative dates and between operators in version 12.5.1.  I am new here, so I would not know if something was the result of a customization.

      I find that in 14.1.3 the GUI will not let me add a second filter referencing the same element.  When I tried adding the same data as a separate element and used <= and >= operators in separate filters, my results had multiple instances of the same constituent.  If I go into TX_QUERY_ELEMENT_VALUES and force the filter to look like it was before the upgrade (SET [value1] = 'DayRunDate +1', [value2] = 'DayRunDate +8', [operator] = 'between'), in the GUI it displays as "With Performance Date between DayRunDate +1 and DayRunDate +8", and the results again have multiple instances of the same constituent (37,000 rows instead of 900).

      My goal is to have this automated via report scheduler with data that does not need massaging each time. It may be time to open a TASK ticket?

    Clarke