关于.rpt: view或schedule时的连接界面及Prompts是否显示的设置
发表于:2024-10-12 作者:千家信息网编辑
千家信息网最后更新 2024年10月12日,BVM修改DC参数[@more@]通过BVM设置DC(即当前rpt所所用的DC):结果:没有设置的情况下:有一个连接参数输入界面,如上图。出现prompts,如下图:修改后:SDN论坛参考:Dynam
千家信息网最后更新 2024年10月12日关于.rpt: view或schedule时的连接界面及Prompts是否显示的设置
When you create a dynamic parameter in a Crystal Report, and then publish it to the Enterprise, you are creating a Business View, with all it's underlying necessary layers. Dynamic Parameters exist to be able to use the same LOV (a list of current customers) from a database for more than one report. These dynamic parameter LOVs act like a mini report that runs against the database and gets the current values for selection, then the selection(s) are used to run the overall report.
So I create a report, and in it I create a dynamic Customer LOV. When I save it, the Enterprise creates a Data Connection (DC), Data Foundation (DF), Business Element (BE), Business View (BV), and the list of values is built on the Prompt Group. So, my Business View Manager, Repository Explorer will show (in the default Dynamic Cascading Prompts folder):
Customer_DC
Customer_DF
Customer_BE
Customer_BV
Customer - Prompt Group
Customer (the LOV)
The idea is that next time I create a report and need a customer parameter, I select the existing dynamic group. If the report designer is unaware of this, and next time they create a new report that needs a customer LOV, they creates a new dynamic LOV "Customer", when saved to the Enterprise, it repeats the above. Since repository objects must have unique names, you will now have additional items something like:
Customer 2_DC
Customer 2_DF
Customer 2_BE
Customer 2_BV
Customer 2 - Prompt Group
Customer 2 (the LOV)
So you can see how that folder will get filled with duplicates pretty quickly. Which ones were created and used in which reports? Have to open the report in Crystal Reports, open the parameter for Edit and verify the LOV name (_2, _3, _4, etc). If you do in fact discover there are dupes, you can change it to a single one for all reports using a dynamic LOV, re-save them to the Enterprise, then delete the dupes in the BVM.
You've already discovered how to use the BVM to update the data connection to include/save the database credentials. The only other common issue is sometimes the LOV rights need to be changed in order to allow users to "Edit" the LOV (select different values in the LOV). You'd have to run the report as an end user, not the admin account or the report designer account to verify that works.
Another item of note is that these dynamic LOVs are run by the Report Application Server (RAS), regardless of which viewer you are using.
The Business View Manager administration guide has more information on the subject.
BVM修改DC参数
[@more@]通过BVM设置DC(即当前rpt所所用的DC):
结果:
没有设置的情况下:
有一个连接参数输入界面,如上图。出现prompts,如下图:
修改后:
SDN论坛参考:
Dynamic Parameters. You'll want to get all your report designers up on this topic.When you create a dynamic parameter in a Crystal Report, and then publish it to the Enterprise, you are creating a Business View, with all it's underlying necessary layers. Dynamic Parameters exist to be able to use the same LOV (a list of current customers) from a database for more than one report. These dynamic parameter LOVs act like a mini report that runs against the database and gets the current values for selection, then the selection(s) are used to run the overall report.
So I create a report, and in it I create a dynamic Customer LOV. When I save it, the Enterprise creates a Data Connection (DC), Data Foundation (DF), Business Element (BE), Business View (BV), and the list of values is built on the Prompt Group. So, my Business View Manager, Repository Explorer will show (in the default Dynamic Cascading Prompts folder):
Customer_DC
Customer_DF
Customer_BE
Customer_BV
Customer - Prompt Group
Customer (the LOV)
The idea is that next time I create a report and need a customer parameter, I select the existing dynamic group. If the report designer is unaware of this, and next time they create a new report that needs a customer LOV, they creates a new dynamic LOV "Customer", when saved to the Enterprise, it repeats the above. Since repository objects must have unique names, you will now have additional items something like:
Customer 2_DC
Customer 2_DF
Customer 2_BE
Customer 2_BV
Customer 2 - Prompt Group
Customer 2 (the LOV)
So you can see how that folder will get filled with duplicates pretty quickly. Which ones were created and used in which reports? Have to open the report in Crystal Reports, open the parameter for Edit and verify the LOV name (_2, _3, _4, etc). If you do in fact discover there are dupes, you can change it to a single one for all reports using a dynamic LOV, re-save them to the Enterprise, then delete the dupes in the BVM.
You've already discovered how to use the BVM to update the data connection to include/save the database credentials. The only other common issue is sometimes the LOV rights need to be changed in order to allow users to "Edit" the LOV (select different values in the LOV). You'd have to run the report as an end user, not the admin account or the report designer account to verify that works.
Another item of note is that these dynamic LOVs are run by the Report Application Server (RAS), regardless of which viewer you are using.
The Business View Manager administration guide has more information on the subject.
参数
界面
上图
情况
所用
结果
论坛
参考
输入
数据库的安全要保护哪些东西
数据库安全各自的含义是什么
生产安全数据库录入
数据库的安全性及管理
数据库安全策略包含哪些
海淀数据库安全审计系统
建立农村房屋安全信息数据库
易用的数据库客户端支持安全管理
连接数据库失败ssl安全错误
数据库的锁怎样保障安全
php数据库数据可视化
网络安全工程师需要学习的指令
沃顿数据库
网络安全和信息化的法律
云数据库买什么配置
网络安全分析师是哪个部门的
centos饥荒服务器
integer数据库长度
oracle软件开发
银行网点 数据库
openwrt服务器自动换
app服务器费用一年要多少钱
数据库建表怎么设置多个主码
大专网络技术能进华为吗
rtp 服务器
海北州软件开发优化价格
数据库原理中授权分为几类
福建曙光服务器维修维保哪家好
监控存储服务器跟录像机一样吗
h3c服务器怎么配置管理
外文题录数据库 知网
本地服务器没有域名
如何在存储服务器上建立数据库
云计算 内存数据库
下载一个数据库多少钱
上海毅翃软件开发有限公司电话
怎么查看自己的网络安全密码
软件开发者选项怎么打开
sw主数据库由于以下错误
有限服务器地址在哪里看