Looking to select a particular performance ID to return a specific set of constituents, and then save that result as a list. Is this something that can be done in analytics yet?
Thanks!
Loccy
Lachlan Hywood
This documentation describes how to do this. https://www.tessituranetwork.com/Help_System/Content/Tessitura%20Analytics/Sharing%20and%20Printing/Save%20to%20List.htm
However at this time on RAMP we are not able to make this work at LSC. We have an open support ticket. We are on Tessitura 15.1.4. Your results may vary
We're on RAMP as well, so looks like I'll need to look for an alternative. Thanks for the info!
I'm not saying that it does not work on RAMP. In fact I expect that this feature should work on RAMP. What I'm saying is that it is not working for me currently, and I have a support ticket open about working on geting this going for LSC.
I invite your to go ahead and test the features described in the documentation sited above. If it is not working for you as well. I'd like to know. But, if it is not working for you I would invite you to open a support ticket.
We are not on RAMP, but have our own servers. However, I cannot get this to work either. I have linked the widget to the constituents jump to dashboard, the icon has appeared but it doesn't appear to do anything.
Hi Tom, Nancy Sheleheda has a support ticket on this as well. We saw this behavior in Pittsburgh several months ago (I believe we were on 15.1.3 then, and are on 15.1.4 now). Although the "undefined" issue was resolved I believe, we're still wrestling with some other odd behavior around saving to list and seeing inconsistencies between the experience in the client vs on the go. For example, at one point it only worked in the client, then it only worked on the go. It is still an open ticket, so I don't see clearly what the issue was/is, but you're not alone in experiencing this.
Yes! We have two sets of TessituraWeb servers... one pair is for 'internal' business and the other is for 'external' business. We had Analytics installed hitting the internal url, and somehow that was the problem. What I had to do was reinstall Analytics so it was using the 'external' TessituraWeb installation, and THEN so we could save to list for both the 'on the go' users vs users in the client, I had to point the TessituraWeb url in our master ini file so it looks to the 'external' TessituraWeb installation. Frankly, I'm not sure our internal TessituraWeb installation gets much play any longer.
Hope this makes sense... happy to chat offline if you like.
Kelly Mednis
Thanks for sharing. We are seeing this problem both inside the client and from on the go.