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
Hi Clarke
Without seeing the element setup in detail, adding the 2nd one of the same element in 14.1 can only be if the element returns a single row - no asterisk.
Using the same element multiple times that doesn't return a single row per constituent is likely what has caused the data problem you mention.
And you're right - it's time to open a TASK ticket!
Cheers
Sandra
Clarke Weigle Just discovering this thread and very thankful for it!
Clarke, have you gotten any update from TASK on this issue?
I created many custom elements in v12 for a scheduled Execute an Output Set solely to use parameters. I can replace them all with standard elements—if I could still use relative start and end dates. Here's hoping!
-- Mike
Hey, Mike!Version 14.1.3 does have relative start and end dates in Output Sets. I loaded it in our Test environment (we are still on 14.1.1), but it did not completely solve our issues, so we gave up on this for the time being. What we are now doing instead is manually setting the parameters on Monday for the Thursday automated reports.
Specifically, I was trying to use scheduled reports with numerous output sets using relative dates with between operators. As you can see above, no lesser authority than Sandra Ashby said that output sets have never been able to use relative dates with between operators. This tells me that, somewhere back in time, my employers paid for some customization, so I will try to find records of who did what when.
Clarke