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?
The original view I created is rendering properly in Tessitura -- the data fields are pulling in -- but they aren't showing up in WordFly.
The fields from the new view I created -- to try to convert the date field without breaking the view that was working -- aren't showing up in Tessitura, so it makes me feel like there is another level of permission that I'm missing.
I'm only seeing one line per constituent in the output of my list, but I'm also using a filter -- is that the issue? I'm starting to think that we may not be able to do this until v16. I need to pull in the most recent membership expiration date for lapsed members. This should be easy in v16, but maybe it isn't possible in v15 (although I feel like someone else must be doing this).
Anne M Robichaux said:but I'm also using a filter -- is that the issue?
Yes, I'm pretty sure that's the problem. If the field is capable of returning more than one row Wordfly will reject it.
Anne M Robichaux said:I need to pull in the most recent membership expiration date for lapsed members.
Not trivial but not impossible. I have a view that does this. If you have multiple membership organizations, you might need to build views/output sets for each.
We only have one membership organization. Would you be willing to share your code for the view?
We had to create a custom "Membership - Most Recent" element for v15. We have several membership orgs with the same start date and that caused issues with the standard Membership - Most Recent view for us. What is the function of the filter you mentioned?
Going to look for it as we speak!