Hoping someone can offer advice about how to troubleshoot this issue. I've got a new SSRS report that contains customer numbers, and I'm having trouble saving as a list. I get an error that says "Cannot create list as report doesn't have any data to be saved".
Here's what I've done so far:
1 - The field name is Customer_No (so that should be ok, right?)
2 - In the properties pane for that field, I've changed DataElementOutput to "Output" and DataElementStyle to "Element".
That's it... should work, right? Or have I missed a step?
Not sure if it makes any difference, but the report in question is a sub-report. I created it starting with a copy of the TessituraReportTemplate that came with v11, though I deleted the header and footer. Any chance there's something important I might have deleted by accident when I did that? Is there something besides those two steps above that need to be done/ be present in the report somewhere?
Any thoughts would be greatly appreciated. Many thanks,
Brian
Try saving the report from WebReports as XML. Do you see Customer_No showing up in the output as an element? If not, check that sub-report is set to output from the main report (in the DataOutput properties for the sub-report).
+Ryan Creps
+Tessitura Network
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Brian Graham Sent: Tuesday, August 27, 2013 2:15 PM To: Ryan Creps Subject: [Tessitura Technical Forum] Trouble with Save as List from SSRS
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
The XML looks correct - the element name is the same there: Customer_No, and it's showing up as an element in carrots <>. I'm not sure about the sub-report. I might have described it wrong. It's a child report - called from an action on a textbox in a main report.