Dear Cognos Gurus,

QueryStudio was a great product. Endusers loved the ease of use. But ... there is a little issue, when migrating to Reportstudio.

Problem Description

Consider a GoSales sample report that includes product groups, product names, and revenue. The product names are stored in English, as the report was originally generated for the Americas region. The report applies a filter on the product group "Golf Equipment".

However, when a French user runs the same report, the product names are automatically translated into French. Because the filter is still looking for the English string "Golf Equipment", the report returns no data-as the translated product group no longer matches the filter condition.

At the database level, product groups are stored using ID columns in the fact tables. These ID columns are indexed for performance, whereas the name columns (such as product group names) are not indexed. Filtering on unindexed name columns leads to significant performance degradation.

Proposed Solution: Filter Item & Display Item

We propose introducing the "Use Filter Item" and "Display Filter Item" features (from Framework Manager Model) into Report Studio.

Previously, in Query Studio, we could associate a query item with separate filter and display items. This allowed reports to filter using efficient, language-agnostic ID columns, while still displaying the user-friendly name columns in the report output.

This dual-layer approach ensures:

• Filters are applied on indexed ID columns (for better performance and language independence).

• Display values are localized (improving usability for international users).

Motivation for Enhancement

We have heavily relied on Query Studio in the past and have fully migrated to Report Studio in the last two years. However, the absence of this functionality in Report Studio presents a significant limitation in multilingual reporting scenarios and degrades performance when using name-based filters. And by the way, this functionality was the most loved feature in QS from our users.

Introducing support for separate display and filter items in Report Studio would:

• Improve performance by leveraging indexed columns for filtering.

• Enable consistent results across language-specific environments.

• Provide a seamless migration path for features previously available in Query Studio.

Call to Action

Please vote in favor of this enhancement CAOP-I-1642 on IBM Ideas. Adopting this functionality in Report Studio will bring much-needed flexibility and efficiency to our reporting solutions.

Thanks for voting for this already quite old idea ;-)

I support to have the ability to, as an admin, create pre-defined filters in Framework Manager / Data Modules and then have an author simply select and click to enable them in a report. You would of course need to ensure that only filters which are applicable at the data query are being shown. So it's not as straight forward as we think.

Dear Cognos Gurus,

QueryStudio was a great product. Endusers loved the ease of use. But ... there is a little issue, when migrating to Reportstudio.

Problem Description

Consider a GoSales sample report that includes product groups, product names, and revenue. The product names are stored in English, as the report was originally generated for the Americas region. The report applies a filter on the product group "Golf Equipment".

However, when a French user runs the same report, the product names are automatically translated into French. Because the filter is still looking for the English string "Golf Equipment", the report returns no data-as the translated product group no longer matches the filter condition.

At the database level, product groups are stored using ID columns in the fact tables. These ID columns are indexed for performance, whereas the name columns (such as product group names) are not indexed. Filtering on unindexed name columns leads to significant performance degradation.

Proposed Solution: Filter Item & Display Item

We propose introducing the "Use Filter Item" and "Display Filter Item" features (from Framework Manager Model) into Report Studio.

Previously, in Query Studio, we could associate a query item with separate filter and display items. This allowed reports to filter using efficient, language-agnostic ID columns, while still displaying the user-friendly name columns in the report output.

This dual-layer approach ensures:

• Filters are applied on indexed ID columns (for better performance and language independence).

• Display values are localized (improving usability for international users).

Motivation for Enhancement

We have heavily relied on Query Studio in the past and have fully migrated to Report Studio in the last two years. However, the absence of this functionality in Report Studio presents a significant limitation in multilingual reporting scenarios and degrades performance when using name-based filters. And by the way, this functionality was the most loved feature in QS from our users.

Introducing support for separate display and filter items in Report Studio would:

• Improve performance by leveraging indexed columns for filtering.

• Enable consistent results across language-specific environments.

• Provide a seamless migration path for features previously available in Query Studio.

Call to Action

Please vote in favor of this enhancement CAOP-I-1642 on IBM Ideas. Adopting this functionality in Report Studio will bring much-needed flexibility and efficiency to our reporting solutions.

Thanks for voting for this already quite old idea ;-)

Not sure about Data Modules, but I am certain that the ability to create "Model Filters" that can be applied to a report via selection from the FM Model already exists.  Giving the filters appropriate names should avoid any confusion as to their usage.

I support to have the ability to, as an admin, create pre-defined filters in Framework Manager / Data Modules and then have an author simply select and click to enable them in a report. You would of course need to ensure that only filters which are applicable at the data query are being shown. So it's not as straight forward as we think.

Dear Cognos Gurus,

QueryStudio was a great product. Endusers loved the ease of use. But ... there is a little issue, when migrating to Reportstudio.

Problem Description

Consider a GoSales sample report that includes product groups, product names, and revenue. The product names are stored in English, as the report was originally generated for the Americas region. The report applies a filter on the product group "Golf Equipment".

However, when a French user runs the same report, the product names are automatically translated into French. Because the filter is still looking for the English string "Golf Equipment", the report returns no data-as the translated product group no longer matches the filter condition.

At the database level, product groups are stored using ID columns in the fact tables. These ID columns are indexed for performance, whereas the name columns (such as product group names) are not indexed. Filtering on unindexed name columns leads to significant performance degradation.

Proposed Solution: Filter Item & Display Item

We propose introducing the "Use Filter Item" and "Display Filter Item" features (from Framework Manager Model) into Report Studio.

Previously, in Query Studio, we could associate a query item with separate filter and display items. This allowed reports to filter using efficient, language-agnostic ID columns, while still displaying the user-friendly name columns in the report output.

This dual-layer approach ensures:

• Filters are applied on indexed ID columns (for better performance and language independence).

• Display values are localized (improving usability for international users).

Motivation for Enhancement

We have heavily relied on Query Studio in the past and have fully migrated to Report Studio in the last two years. However, the absence of this functionality in Report Studio presents a significant limitation in multilingual reporting scenarios and degrades performance when using name-based filters. And by the way, this functionality was the most loved feature in QS from our users.

Introducing support for separate display and filter items in Report Studio would:

• Improve performance by leveraging indexed columns for filtering.

• Enable consistent results across language-specific environments.

• Provide a seamless migration path for features previously available in Query Studio.

Call to Action

Please vote in favor of this enhancement CAOP-I-1642 on IBM Ideas. Adopting this functionality in Report Studio will bring much-needed flexibility and efficiency to our reporting solutions.

Thanks for voting for this already quite old idea ;-)

It definitely already exists, but not in a way that it is showing filters per base query subject.

Would be extremely nice that if you take elements in your query from query subject QA in your report query, you can see a list of filters only applicable on QA. Add a QB element, and you will also see QB filters in the list.

That will reduce outer joins chances and make it much more intuitive to use, and i thought that was a bit the topic here. But maybe i'm wrong;)

Not sure about Data Modules, but I am certain that the ability to create "Model Filters" that can be applied to a report via selection from the FM Model already exists.  Giving the filters appropriate names should avoid any confusion as to their usage.

I support to have the ability to, as an admin, create pre-defined filters in Framework Manager / Data Modules and then have an author simply select and click to enable them in a report. You would of course need to ensure that only filters which are applicable at the data query are being shown. So it's not as straight forward as we think.

Dear Cognos Gurus,

QueryStudio was a great product. Endusers loved the ease of use. But ... there is a little issue, when migrating to Reportstudio.

Problem Description

Consider a GoSales sample report that includes product groups, product names, and revenue. The product names are stored in English, as the report was originally generated for the Americas region. The report applies a filter on the product group "Golf Equipment".

However, when a French user runs the same report, the product names are automatically translated into French. Because the filter is still looking for the English string "Golf Equipment", the report returns no data-as the translated product group no longer matches the filter condition.

At the database level, product groups are stored using ID columns in the fact tables. These ID columns are indexed for performance, whereas the name columns (such as product group names) are not indexed. Filtering on unindexed name columns leads to significant performance degradation.

Proposed Solution: Filter Item & Display Item

We propose introducing the "Use Filter Item" and "Display Filter Item" features (from Framework Manager Model) into Report Studio.

Previously, in Query Studio, we could associate a query item with separate filter and display items. This allowed reports to filter using efficient, language-agnostic ID columns, while still displaying the user-friendly name columns in the report output.

This dual-layer approach ensures:

• Filters are applied on indexed ID columns (for better performance and language independence).

• Display values are localized (improving usability for international users).

Motivation for Enhancement

We have heavily relied on Query Studio in the past and have fully migrated to Report Studio in the last two years. However, the absence of this functionality in Report Studio presents a significant limitation in multilingual reporting scenarios and degrades performance when using name-based filters. And by the way, this functionality was the most loved feature in QS from our users.

Introducing support for separate display and filter items in Report Studio would:

• Improve performance by leveraging indexed columns for filtering.

• Enable consistent results across language-specific environments.

• Provide a seamless migration path for features previously available in Query Studio.

Call to Action

Please vote in favor of this enhancement CAOP-I-1642 on IBM Ideas. Adopting this functionality in Report Studio will bring much-needed flexibility and efficiency to our reporting solutions.

Thanks for voting for this already quite old idea ;-)