I have a stakeholder who has a really strong interest in controlling colors in a Stacked Column visualization - I'm using Cognos v11.2.3 and using the canned Stacked Column graph found in the "11.0 visualization" gallery.

This can't be solved just by changing the Palette as this stakeholder wants me to set specific colors for each of the 10 known text values which represent the Segments in the columns.  Like when the related data field has a value of "Low" color the related segments (and legend) as yellow. 

If this isn't an option available with the 11.0 visualizations, can this be done using graphs from other galleries like maybe the really old-school canned graphs from v10?

Hi

I had similar experience when it was upgraded two years ago. Couldn't figure out what to do so I deleted that chart, saved the report, closed the report, open the report again and make the chart again.

Dear forum user,

we are experiencing an issue with the Cognos Analytics App within Microsoft Teams when attempting to publish content to a chat.

Problem Description

The Cognos Analytics App in MS Teams (App and Webclient) is unable to provide the URL input field for publishing content specifically within a personal or group chat. Instead, a loading screen appears and eventually times out. Publishing content to a Teams Channel, however, works without problems.

Environment Details

• MS Teams Version: Not explicitly stated, but the issue occurs within the MS Teams client.
• Cognos Analytics Version: 12.0.4 Interim Fix 3
• Application State: The application-side configuration has remained unchanged for a long period.
• Firewall: Verified and confirmed to be fully functional.
• Troubleshooting Steps Taken: A fresh deployment using a current App Manifest was performed, but it did not resolve the issue.
  

Observed Behavior

No changes were made to our environment, and suddenly, the following behavior began occurring:

Positive Observation / Working

Using the Cognos Analytics App, we can successfully access Cognos and publish content to a Microsoft Teams Channel. This functionality works as expected.

Negative Observation / Error

When attempting to publish content in a Microsoft Teams personal Chat, the Cognos URL input field for publication is missing.
Instead of the expected input field, a loading screen is displayed (as shown in `2_input_url_is_missing.png`).
This loading screen eventually times out, resulting in an error message stating: "There was a problem reaching this app." (as shown in `3_Timeout.png`).

Screenshots

To illustrate the issue, we have attached the following screenshots:

`1_personal_chat_select_cognos_app.png`: Shows the initial step where the Cognos Analytics app is selected within a personal chat.
`2_input_url_is_missing.png`: Displays the loading screen that appears instead of the Cognos URL input field.
`3_Timeout.png`: Shows the error message displayed after the loading screen times out.


Best regards,
Roberto

Hello All,

One of the user has reported, his my content personal templates are missing.

When we checked in the AD group, his profile is in place and folders in team content are there.

Note: Till early December, he was able to see the templates and later he has switched to cloud pc which is reprovisioned.  His user is same and there is no change in that.

Please advise, how to find and restore the templates.

Hi

Uniqueidentifier in Cognos is specific to Framework Manager and is used to tell Cognos that the field will be used in joins and in conjuction with Determinants, Cognos will generate the appropriate SQL accordingly. Uniqueidentifier ca work with Numeric, Character etc. but that being said MD5 Hash may or may not work because it is considered unsafe and broken. MD5 also cannot be entirely binary because it can contain alphabets too during it's generation. 

Uniqueidentifier in databases refers to a varchar type of field (GUID - Globally Unique Identifier) which is globally unique across the database, not across the table. While this is good for data integrity but it's really bad for the performance of the query because of it's size.

Depends on where you want to apply this. Outside of modelling in FM, you can definitely use the MD5 field in a hand written SQL to join the Fact and Dimension tables. Hand written SQLs do not face limitations of the Cognos versions

As the title says, I'm wondering if Cognos version 12+ supports binary fields as key fields between tables?
For example, an MD5 hash is used as the primary key to join the fact and dimension tables.
What about uniqueidentifier types instead of binary?

Hi @deetchiga ,

Is the issue solved, can you please let me know the reason?

Regards,
Sreeni.

Hi @dougp

Tried that too still same issue.

Regards,
Sreeni.

On the command line you use to call trigger.bat, have you tried putting quotes around the password?

Hi All,

We have setup trigger concept in our cognos vm, when we try to test it fails with below error:

Tried things:
1. Changed password from special characters to plain password(alpha numeric)
2. Tried service account tagged to system admin role
3. Also scheduling and run with options capability explicitly defined for sys admin.
4. Same service account able to login from Cognos UI.
5. Tried individual user access same below error.

So basically when we try to trigger it using trigger.bat we are facing this issue.

Please provide your thoughts.


AxisFault
faultCode: Client
faultSubcode:
faultString: CM-REQ-4342 An error occurred with the client.
faultActor:
faultNode:
faultDetail:
{http://developer.cognos.com/schemas/bibus/3/}exception:
<severity>error</severity>
<errorCode>caf</errorCode>

<ns1:message><messageString>CM-CAM-4005 Unable to authenticate. Check your security directory server connection and confirm the credentials entered at login.</messageString></ns1:message><ns1:message><messageString>CAF-WRN-2082 An error has occurred. Please contact your administrator. The complete error has been logged by CAF with SecureErrorID:2026-03-03-05:07:49.245-#25</messageString></ns1:message>

CM-REQ-4342 An error occurred with the client.
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:610)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1718)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2883)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:605)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112)
at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:534)
at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:888)
at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:824)
at java.xml/com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1216)
at java.xml/com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:635)
at java.xml/com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:324)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:698)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.cognos.developer.schemas.bibus._3.ContentManagerServiceStub.logon(ContentManagerServiceStub.java:8165)
at Trigger.login(Trigger.java:111)
at Trigger.main(Trigger.java:276)