I wanted to change visibility of a object on the basis of number of recods which Report Query gets.
我想更改对象的可见性基于报告查询获取的重新编码的数量。
For example, some business requirements are generated by analyzing existing report query workflows and interpreting current business data analytic structures.
例如，某些业务需求是通过分析现有报表查询工作流和解释当前业务数据分析结构而生成的。
Often it is obvious to the report manager that the embedded prompt will not be needed to evaluate the report query and so the additional filter information is superfluous.
通常对于报表管理器很明显的是，评估报表查询不需要嵌入式提示，因此附加的过滤器信息是多余的。
For this scenario, the report cannot be altered to produce the same in both query modes.
对于这个场景，不能修改报告以在两种查询模式下都生成相同的输出。
The content of a particular report is determined by a dynamic SQL query to one or more data sources.
特定报告的内容是由对一个或多个数据源发出的动态SQL查询确定的。
The database structure needs to hold the survey results and then enable you to query and report on the data that has been stored.
数据库结构需要能够保存问卷调查的结果，然后允许您对所存储的数据进行查询和报告。
For most AD hoc query users or report authors, they provide little benefit and can cause confusion.
对于大多数特殊查询用户或报告编写者而言，这是毫无益处的，而且可能引起混淆。
Sometimes customers report a performance problem where a specific query is not performing optimally.
有时候客户报告的性能问题中说某个特定查询的执行没有优化。
I often create a simple report rather than a work item query when I need to include information from many different sources.
当我需要包含来自许多不同来源的信息时，我通常会创建一个简单的报表，而不是一个工作项查询。
The scenario below illustrates the difference in outputs of running the same report in both query modes.
以下场景说明在两种查询模式下运行同一报表所产生的输出的不同。
Designing reports without data allows authors to add all the items required for the report before submitting a query to the data source.
无数据设计报表能让设计人员在向数据源提交查询之前添加报表所需的所有项目。
The reports are a combination of a report format, combined with a defined query.
该报告是报告格式和定义需求的结合体。
Report and query processing will be influenced by both the number of Concurrent users as well as by the complexity of your application.
报告和查询处理将受Concurrent用户数量和您应用程序复杂性的影响。
Executing the same report in Dynamic Query Mode produces the following error message.
以dynamicQueryMode执行以下报告将生成以下错误消息。
Dynamically updating query to drive the charts and report.
动态地更新查询来驱动图表和报告。
If this same report is executed using Dynamic Query Mode, it returns multiple rows for the 100 ml product size.
如果以dynamicQueryMode执行这个报告，将返回多行产品大小为100ml的记录。
To execute this report in Dynamic Query Mode without errors, you can apply the filter to the Product type level using the following expression.
要以DynamicQueryMode正确执行报告，可以使用以下表达式，将过滤器应用到Producttype级别。
Here is an example of an OCL query, using the optional OCL report manifest entries.
下面是一个OCL查询的例子，使用可选择的OCL报告显示入口。
When this report is executed using Compatible Query Mode, it returns one row for the 100 ml product size.
以CompatibleQueryMode执行报告时，会返回一行产品大小为100ml的记录。
When this report is executed in Dynamic Query Mode, it produces the following error message.
以dynamicQueryMode执行这个报告将生成以下错误消息。
For your report, you need two query subjects in the Cognos project that you then join to obtain a textual description for each outlier.
对于这个报告，Cognos项目中需要两个查询主题，然后通过连接它们获得每个离群值的文本描述。
When the report is validated using Compatible Query Mode it displays the following warning message.
以 CompatibleQueryMode 执行报告时，会显示以下警告消息。
You have created the query subjects you need for the Cognos report.
您现在已经创建了用于Cognos报告的查询主题。
When executed in Compatible Query Mode, the report displays all Product types which do not start with the letter 'c'.
以CompatibleQueryMode执行时，报告显示所有不以字母c开头的Producttypes。
Running the same report in Dynamic Query Mode produces the following error message
在DynamicQueryMode执行相同的报告会生成以下错误消息
Create a new report for the detailed report and create a data set with query like this.
为详细报告创建一个新的报告，并用如下所示的查询创建一个数据集。
BW SAP query Embedded in email The report delivery is made available as part of.
BWSAP查询内嵌在电子邮件中这种报告交付作为以下内容的一部分获得。
BW SAP query ZIP The report data is delivered as part of.
BWSAP查询ZIP报告数据作为以下内容的一部分交付。
BW SAP query MHTML The report data is delivered as part of.
BWSAP查询MHTML报告数据作为以下内容的一部分交付。
Planning for report and query processing is the most important consideration if you're looking to supply a highly performing Cognos solution.
如果您正在寻找支持一个高可用性能的Cognos解决方案，作出报告和查询处理计划是最重要的考虑因素。
应用推荐