If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Recent posts

#81
Framework Manager / Re: [Update 12.0.4 FP1] Prompt...
Last post by Xenobiologist - 10 Feb 2025 01:59:45 AM
Sorry, it took some time.
IBM has confirmed the bug here: https://www.ibm.com/mysupport/s/defect/aCIKe000000XqNw/dt422363?language=en_US
#82
Reporting / Insertable objects only create...
Last post by telapan - 07 Feb 2025 12:06:15 PM
Hi all,

I'm using IBM Cognos Analytics 11.1.7 web UI. I have an existing List that contains data from a query. When I try to add any additional fields from the query the List only a column header is created. No data is added to the List and I can' modify the column to include data. I feel like the list is corrupted some how but not sure how to move past this issue.

Any help is appreciated.

Taylor
#83
Report Studio / Re: Unable to use value prompt...
Last post by dougp - 07 Feb 2025 10:59:32 AM
QuoteThe prompts use different queries.

I assume the queries are different.  Otherwise, use the same query to simplify the report.


QuoteDEfualt should be all.

What does that mean?


Can you reproduce the problem using the samples (Go Sales (query)) and post the report spec so we can see what the problem looks like?
#84
Report Studio / Unable to use value prompt and...
Last post by actcognosuser - 07 Feb 2025 08:43:12 AM
Report has both value prompt and search and select prompt which are both set to optional and multiselect.

The prompts use different queries. Field is orderid

User should be able to select Orderid from the value prompt or search /select prompt or both. DEfualt should be all.

When I use this detail filter the select all option and input box for search prompt disappeared.

(
(paramcount(?SearchOrderid?)=0 OR [ORDER ID] in (?SearchOrderid?))

AND

(paramcount( ?SelectOrderid? )=0 OR [ORDER ID] in (?SelectOrderid?))
#85
Announcements / Unlocking Full Report Lineage ...
Last post by DaBaker - 06 Feb 2025 10:24:05 AM
Unlocking Full Report Lineage in IBM Cognos Analytics: Query Items and Beyond

In today's data-driven world, organizations rely on business intelligence (BI) platforms like IBM Cognos Analytics to extract meaningful insights. However, as reports grow in complexity, understanding their lineage—how data flows from source to final visualization—becomes crucial. Full report lineage provides transparency, aiding administrators, developers, and analysts in troubleshooting, optimizing performance, and ensuring data governance.

Understanding Report Lineage in Cognos Analytics
IBM Cognos Analytics offers built-in capabilities to track report lineage, helping users trace data back to its source. However, traditional lineage views often stop at the data module or package level, making it difficult to see how individual query items contribute to the final report output. This is where enhanced lineage tracking becomes invaluable.

By extending report lineage to include query items, organizations can:
- Gain deeper visibility into report dependencies.
- Identify and resolve data discrepancies faster.
- Ensure compliance with data governance policies.
- Improve collaboration between business users and IT teams.

Enhancing Lineage with BSP Software's MetaManager
BSP Software's MetaManager extends the lineage tracking capabilities of Cognos Analytics, offering a more granular view of report components. With its Full Report Lineage functionality, users can:
- Track query items from source databases to final report elements.
- Visualize data relationships across multiple Cognos objects.
- Identify redundant or underutilized data sources.

By leveraging MetaManager's automated lineage extraction, organizations can significantly reduce the manual effort required for impact analysis, ensuring faster and more accurate decision-making.

Practical Applications of Full Report Lineage
1. Troubleshooting Report Issues
When reports return unexpected results, understanding which query items contribute to the output can help pinpoint issues. Full lineage tracking enables quick identification of misconfigured joins, filters, or calculations.

2. Optimizing Report Performance
Large reports often suffer from slow execution times due to inefficient queries. By analyzing lineage, developers can detect unnecessary query items, optimize SQL generation, and enhance overall performance.

3. Strengthening Data Governance
Regulatory compliance and internal governance policies require organizations to maintain full visibility into how data is sourced and transformed. Extended report lineage ensures that every data point can be traced, reducing compliance risks.

4. Supporting Migration & Upgrades
When upgrading Cognos environments or transitioning to new data sources, lineage analysis helps assess dependencies and minimize disruptions.

The Future of Report Lineage in Cognos Analytics
As organizations continue to scale their BI capabilities, the demand for deeper lineage insights will grow. Enhancements like those offered by BSP Software's MetaManager empower Cognos Analytics users with greater control over their data, ensuring more reliable and efficient reporting.

By integrating full report lineage tracking into your Cognos workflow, you can unlock new levels of transparency, performance, and governance—positioning your organization for long-term BI success.

For more information on extending Cognos Analytics capabilities, visit BSP Software's MetaManager suite or find a BSP Blog.
#86
UNICOM PowerHouse / How many shops still use Cogno...
Last post by javr - 05 Feb 2025 11:17:09 AM
I know that the government of British Columbia is still using Powerhouse on OpenVMS for student data. They have migrated a lot of functionality to Java and continue to do so.

Not being a Java developer, I am re-training in the AI area myself.

Thanks for any comments people care to leave.
#87
Reporting / Grouping isn't working in Cong...
Last post by Bago - 04 Feb 2025 06:59:39 AM
I have 2 Items is duplicated in the report this items is shared across the Organization (4 org IDs) and shows is it zero stock or not

also, I create a data item to detect if its zero in this (A) ORG or not and did this to all organization (B) and (C)

Note: (ORG C) is a TWO Stock have different ORG ID location is deferent but they are one


the issue I'm having is:

there is Two item when I run the report xls. give me duplicate result


what I did is I but each Organization in SQL Query then I join them with 0n = 0n relation

1- (ORG A)JOINED WITH (ORG B) CREATING query Named MED

then some of the data items I need to not duplicated data and avoided null values I did this condition and give it name Planner code
 
case
when(    [PLANNER_CODE_ORG_A] is null)then([PLANNER_CODE_ORG_B])
else ([PLANNER_CODE_ORG_A])
end




Then I joined the query (MED) with (ORG C) and did the same as above to include all the Organization Planner code

Note: all the columns in the queries are the same



Report Duplication Issue:

I am encountering a duplication issue in my report concerning two items that are shared across four organizations (ORG A, ORG B, ORG C, and ORG D

*ORG C &D are the same but different location have different ORG ID *).

These items indicate whether stock levels are zero or not.



Summary of the Approach:


SQL Query Structure:

I structured my SQL queries to avoid duplication:

Joined ORG A with ORG B, creating a query named MED. with relation 0n = 0n

To handle potential null values and prevent blank in the report, I implemented a condition for the required columns example planner code:

CASE
  WHEN [PLANNER_CODE_ORG_A] IS NULL THEN [PLANNER_CODE_ORG_B]
  ELSE [PLANNER_CODE_ORG_A]
END AS Planner_Code

then Final Join:
The MED query was then joined with ORG C, applying the same logic to include the planner codes from all organizations.


Current Challenge:
Despite these measures, the report still generates duplicate results for two items when exporting to XLS.

here is attached photo




 



 
#88
Hi Cognos Community !

Urgent !!!

One of our On-Prem Oracle Database has been migrated to Oracle Cloud (ADW)

We are in the phase of testing our Cognos Data Source Connection to Oracle ADW.

we obtained tns entries (host, port, service name) for this cloud DB

Below things we have in our Cognos servers.

1) Oracle Client v12.1.0.2

2) ojdbc8.jar (v21.6.0.0.1)


As part of testing, we have created new Data Source Connection in Cognos DEV environment and provided all the connection parameters.

OCI connection is getting succeeded but we are facing challenges for JDBC connection.

Does anyone has idea on how to create Data Source Connection from Cognos v11.0.12 to Oracle ADW Cloud DB ?

Looking forward for your inputs and guidance..

Thanks,

Lokeswara


#89
Reporting / Displaying a Solid Color Box
Last post by pechmo - 30 Jan 2025 08:25:13 AM
I have a report with several bar charts and need to display custom legends below each.  What's the best way to create a set of small square boxes that correspond to the colors of the bars on my bar charts?  I've tried using a Text Item, a Block, and an Image.  All of them do what I want but I want to do whatever is most efficient time-wise because I'll be bursting this report to create 1000s of PDFs and every millisecond counts.
#90
Cognos Analytics / MOVED: Columns replicating dat...
Last post by MFGF - 29 Jan 2025 12:13:02 PM