Hello,
I'm trying to change the date format in a query element to make it user friendly for WordFly and I can't seem to get it work. Looking at the documentation, I should be able to use the CONVERT function in the system table to do so, but I'm getting an error. Alternatively, I tried setting up a new view and did the conversion there and that seems to work, but I can't get the elements in the new view to pull into my output set. I've granted SELECT permissions to ImpUsers and Tessitura_App and WordFly in SSMS.
And also related -- even when I have the output set working (with the dates in the wrong format, but the data pulling in from another view), WordFly can't seem to find those fields -- can it not use custom output elements? They aren't showing up as fields to be mapped.
Anne
Sometimes the embedded SQL code options in parts of Tessitura are more limited in syntax options than TSQL itself: I'm often stymied in my attempts to do something clever (most recently setting up disable clauses in report parameters). So I would then go with a view, as you have. Now, the output set elements are displaying properly within Tessitura, right? The first thing I'd think of with Wordfly rejecting an element is that Wordfly will not accept elements that may result in multiple rows. Is that the case here, or is the element configured in such a way that it looks like it might return multiple rows? Is the whole output set failing to be picked up in Wordfly or only that column?
And the documentation says you can use CONVERT in Query Elements, which is the only reason I tried it.