报表生成器 3.0 的限制
我正在构建一个应用程序，客户要求提供报告。通常我们会使用报告服务为他们创建报告。我们希望为客户提供报告构建器，让他们构建自己的报告。其中一些报告可能很复杂，我不能 100% 确定报告生成器将带我们走多远。
在我们决定是否值得向客户提供报告生成器之前。报告生成器有哪些限制？它不适合什么类型的报告？
I am building an application and the client is asking for reports. Normally we would create the reports for them using reporting services. We are wanting to give the client report builder and let them build there own reports. Some of these reports can be complex and I am not 100% sure how far report builder will take us.
Before we decide if it’s worth giving the client report builder. What are the limitations of report builder? What type of report is it no good for?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我发现它非常适合创建和管理要放置在报表服务器上的报表。您显然不能将其用于 .rdlc 报告。对于大多数标准用户和高级用户来说，它就可以满足他们的需要，并且不需要 SQL Server (BIDS) 附带的整个 VS IDE shell。
请记住，如果客户要求管理自己的报告，那就是一种“全有或全无”的情况。您无法限制他们对数据的访问。确保他们在服务器上设置了只读报告帐户。您最初为他们创建的任何报告都会被备份。
培训时间可能会有所不同，具体取决于最终用户预期使用该工具的技术水平。
I found it is fine for creating and managing reports to be placed on the report server. You obviously cannot use it for .rdlc reports. For most standard users and power users it will be just fine and do what they need, and will not require the entire VS IDE shell that comes with SQL Server (BIDS).
Just remember, if the client is asking to manage their own reports, it's kind of an "all or nothing" situation. You cannot limit their access to the data. Make sure they have a read only reporting account set up on the server. Any reports you create for them originally are backed up.
Train up time may vary depending on the technical level of the end-user expected to use the tool.