• Replies 19 replies
  • Subscribers 338 subscribers
  • Views 774 views
  • Users 0 members are here
Related

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

Christopher Sherwood
$organization

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
  • $organization

    Hi Chris,

    For your Output Filters, creating code as you suggested could be entered directly into TX_QUERY_ELEMENT_VALUES. Making this type of manual update will not allow you to open the Output Set from the application, but would give you the ability to run the queries and return the data for your Constituents. In v15 we will have the feature available to filter Output Set elements using relative dates from within the application.

    Karen

Reply
  • $organization

    Hi Chris,

    For your Output Filters, creating code as you suggested could be entered directly into TX_QUERY_ELEMENT_VALUES. Making this type of manual update will not allow you to open the Output Set from the application, but would give you the ability to run the queries and return the data for your Constituents. In v15 we will have the feature available to filter Output Set elements using relative dates from within the application.

    Karen

Children