Cognos Analytics

 View Only

 CA 11.2.4: Remove extra-hexadecimal characters (9) in the report output name

  • IBMChampion
Patrick Neveu's profile image
Patrick Neveu IBM Champion posted Mon March 03, 2025 06:10 AM

Hi,

My customer is using Cognos Analytics 11.2.4 (2406211735, aka FP4).

When he creates a report output, the reportname looks like "reportname abc456def.xlsx" where abc456def is a random hexadecimal string of 9 characters.

I have been able to reproduce with supported browsers and with other outputs : PDF, CVS.

I am not using burst features and I am not trying to save the report output to the file system (cm.outlocation is not used).

I did not find any parameter to remove this hexadecimal string.

Best regards,

Patrick Neveu's profile image
Patrick Neveu IBM Champion posted Fri March 07, 2025 03:07 AM

Hi,

I've created a case with IBM Support: TS018679368

Best regards,

Patrick Neveu

Patrick Neveu's profile image
Patrick Neveu IBM Champion posted Mon March 10, 2025 11:30 AM

Hi,

Here is the answer from IBM support:

This occurs when you have set the temporary object location to 'Content store'.

Check if they have this setting on. If yes, then the behaviour is expected.

https://www.ibm.com/docs/en/cognos-analytics/11.1.0?topic=cml-reducing-content-manager-load-by-storing-user-session-files-locally

If you dont want the files with those additional appendages, then set the temporary object location to 'Local File System':

If set to content store, then CM will always add those additional alphanumeric chars at the end to distinguish each saved temp output.

Wayne Westlake's profile image
Wayne Westlake posted Mon March 10, 2025 03:16 PM

Interesting.  Though we're not experiencing this issue I wanted to make sure the Content Store wasn't being used for temporary stuff.  Though there have been about a dozen upgrades since 8.4.1 and one full export/import, my server was still set to Server File System.  That IBM doc seems to imply if you've done an upgrade it switches to the Content Store and has to be manually set back.  Maybe that was an old bug?

Anyway, glad IBM support gave you the info to help your customer.

Regards,

Wayne

Related Content