• Replies 19 replies
  • Subscribers 338 subscribers
  • Views 760 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 All
     
    In the meantime, until you get to v14.1.3, if you haven’t already done this, I believe this is the most straightforward way to have elements with relative dates. I’ve used Performance Reminder as the example looking at 4 to 7 days from the run date.
     
    The Data_Where in the Group is acting as the Filter.
     
    For the elements that need relative dates, you should make new Groups and Elements, and name them so it is obvious to other users what they are for.
     
    If you do use this PLEASE TEST FIRST before using in Live !!!
     
    Hope this helps.
    Sandra
     
    Group grid
     

    Column Name

    Example Value

    Description

    Perf Reminder - relative dates

    Data_From

    VS_ELEMENTS_TICKET_HISTORY

    Data_Where

    !.perf_dt >= DateAdd(dd, 4, CONVERT (VARCHAR, GetDate(), 112)) AND !.perf_dt <= DateAdd(dd, 7, CONVERT (VARCHAR, GetDate(), 112) + ' 23:59:59.997')

    Virtual Ind

    [Unchecked]

    Category

    Ticketing
     
    Element grid

    Column Name

    Example Value

    Description

    Performance Name

    Group Id

    Perf Reminder - relative dates

    Data_Select

    !.perf_name

    Single_row

    [Unchecked]

    Primary Group Default

    [Unchecked]
     

    Column Name

    Example Value

    Description

    Performance Date

    Group Id

    Performance Reminder

    Data_Select

    !.perf_dt

    Single_row

    [Unchecked]

    Primary Group Default

    [Unchecked]
     
     
     
     
Reply
  • $organization
    Hi All
     
    In the meantime, until you get to v14.1.3, if you haven’t already done this, I believe this is the most straightforward way to have elements with relative dates. I’ve used Performance Reminder as the example looking at 4 to 7 days from the run date.
     
    The Data_Where in the Group is acting as the Filter.
     
    For the elements that need relative dates, you should make new Groups and Elements, and name them so it is obvious to other users what they are for.
     
    If you do use this PLEASE TEST FIRST before using in Live !!!
     
    Hope this helps.
    Sandra
     
    Group grid
     

    Column Name

    Example Value

    Description

    Perf Reminder - relative dates

    Data_From

    VS_ELEMENTS_TICKET_HISTORY

    Data_Where

    !.perf_dt >= DateAdd(dd, 4, CONVERT (VARCHAR, GetDate(), 112)) AND !.perf_dt <= DateAdd(dd, 7, CONVERT (VARCHAR, GetDate(), 112) + ' 23:59:59.997')

    Virtual Ind

    [Unchecked]

    Category

    Ticketing
     
    Element grid

    Column Name

    Example Value

    Description

    Performance Name

    Group Id

    Perf Reminder - relative dates

    Data_Select

    !.perf_name

    Single_row

    [Unchecked]

    Primary Group Default

    [Unchecked]
     

    Column Name

    Example Value

    Description

    Performance Date

    Group Id

    Performance Reminder

    Data_Select

    !.perf_dt

    Single_row

    [Unchecked]

    Primary Group Default

    [Unchecked]
     
     
     
     
Children