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

Christopher Sherwood $organization over 8 years ago

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

Sandra Ashby $organization over 7 years ago

Clarke - In 14.1.3, you should be able to achieve the Between using 2 Filters (see below) and schedule reports to run the output sets with relative dates. Or are you trying to achieve something else completely different?

Contribution Date >= [relativeDate]

Contribution Date <= [relativeDate]

Also an apology to ALL – I had a brain implosion regarding BETWEEN and previous versions of Output Set Builder. Yes you could use relative dates for the start and end date parameters in the where clause associated to the Element. The brain was obviously fixating on List Manager where relative dates and Between have never been possible. It appears I am fallible … on the odd occasion 😊

Cheers

S.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Reply

Sandra Ashby $organization over 7 years ago

Clarke - In 14.1.3, you should be able to achieve the Between using 2 Filters (see below) and schedule reports to run the output sets with relative dates. Or are you trying to achieve something else completely different?

Contribution Date >= [relativeDate]

Contribution Date <= [relativeDate]

Also an apology to ALL – I had a brain implosion regarding BETWEEN and previous versions of Output Set Builder. Yes you could use relative dates for the start and end date parameters in the where clause associated to the Element. The brain was obviously fixating on List Manager where relative dates and Between have never been possible. It appears I am fallible … on the odd occasion 😊

Cheers

S.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Children

Clarke Weigle $organization over 7 years ago in reply to Sandra Ashby

Sadly, we no longer have 14.1.3, so I can't even test it (our Live server died suddenly, so the Test machine became the production environment). Your solution above solves the problem that was our only motivation to upgrade.

I had a problem making it work in 14.1.3, but I am pretty sure it was my sloppy coding and not the program. The output set has to return both the performance date and the performance name, so the idea of putting the where conditions on the group level works better all around.

Clarke
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel