I was wondering if anyone else is experiencing the same problem. We recently upgraded from Cognos 10.2 to Cognos 11 and now we are experiencing the issue that an extra row is added automatically top the of reports in the Excel output.
It seems to be an automatic page number, but this is not needed or desired by my customer for Excel reports.
This is even happening to me in blank reports with no template specified.
I would like to know if this is a bug, or if there is a setting somewhere that one could change?
Cognos will only do this if you are working in design mode. Try saving the report, and running it outside of design mode.
Related
The method ExportAsFixedFormat in Microsoft.Office.Interop.Excel is no longer exporting any graphics or formatting to the PDF file. The code has not changed.
This method worked in my development debug environment as recently as July 9th 2019 using the Interop Library (version 15) in Visual Studio 2017.
It also worked as recently as July 16th in the production environment using an installation of Office 2013, and has been working in Production since April.
I'm building a report in Excel with Charts, a logo.jpg image and I am formatting column widths, row heights, and adding thickened borders around some of the cells. This is all saved in an Excel document first and then exported to PDF using the method above.
When I was asked to manually generate the report for a new client on July 23rd, I determined that the above charts, the image and the formatting were all excluded from the output in the PDF, although the data and font changes were exported. It's pretty ugly though.
So far...
I confirmed that it is no longer working in either environment (Development or Production) so whatever changed not only changed the office 2013 installation, but the Interop library in Visual Studio. (MS Update maybe?)
I tried downgrading the library to version 14 (instead of 15), and then tried upgrading it to 15.4795.1000 and neither of those work.
Manually using SaveAs from within Excel 2013 has the same result, but not really a valid test because I never tried it manually in the first place.
I searched for documentation on Microsoft updates, they did update Excel 2013 to fix two remote code execution vulnerabilities, but I'm not sure where to look that would tell me that the method ExportAsFixedFileFormat was changed and now requires "X". Although I did re-read the docs on the method to see if I was missing anything.
I wasn't using XLFixedFormatQuality, but added it just in case and that had no impact on the issue.
The Code is fairly straightforward and as mentioned, it was working just fine, it still exports and creates a PDF file, the file is just text data only though and only the Font Formatting made it through the export.
xlWorkBook.ExportAsFixedFormat(Excel.XlFixedFormatType.xlTypePDF, ParamValues(3), Excel.XlFixedFormatQuality.xlQualityStandard)
The Filename is stored in ParamValues(3).
There are no errors, no exceptions generated, with the exception of a loss of formatting, charts and images in the final product, the application behaves just as it always has.
After further speculation and testing, we determined that it was printer driver related. I had installed a generic text/only printer to test something I had been working on and Win10 was set to "manage" my default printer by setting my default to whatever printer I most recently used.
Using RDP into the production machine was bringing this default printer with me into the setting and the Export method was using that printer driver to generate the PDF
Hi
We have a couple of issues that might be bugs. At least we cannot find any fixes or help on the web.
We have an Excel sheet with a sheet per Entity. All data comes from the same MDS.
Screenshot of MDS spreadheet
First problem
When we close the spreadsheet and open it again. We connect to MDS again but it is like some of the tabs/sheets does not connect again. The refresh button and publish button is greyed out (see screenshot - I have scrolled away from all the sensitive data). Any tips to fix this would be great!
Second problem
When above fails we would try to refresh the data fully from the MDS Explorer in Excel. However then it renames the sheet-tab and adds a number "1" at the end? (See Account 1 in screenshot) Is there any way to control this as renaming screws up the sheet for us?
Third Problem
This is harder to explain and it is a periodical problem - I cant find any way to really trigger it. So I just hope someone have seen this as well and found a fix for it.
What happens is, while scrolling in one of the Entity sheets suddenly the first two lines which normally is split and freezed suddenly starts scrolling with data from the same sheet? So if you see the screenshot and imagine the 1-2 suddenly shows row 1050-1051 and scrolls as well with the normal rows.
Hard facts about the systems:
<pre>
DatabaseSchemaVersion
13.1.0.3
SQLServerVersion
Microsoft SQL Server 2016 (SP1-CU5) (KB4040714) - 13.0.4451.0 (X64)
Sep 5 2017 16:12:34
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows Server 2016 Standard 6.3 <X64> (Build 14393: ) (Hypervisor)
ProductVersion
13.1.0.3
CompatibilityLevel
110
OSVersion
Microsoft Windows Server 2016 Standard
Excel Version
16.0.4705.1000
Excel Add-in Version
13.0.5150.0
</pre>
So please any help, pointing in the right direction, or explanation will be received on my knees kissing your hands :)
I did not have problem with Performance Point grids before. I could do various things on grids like change report type, change layout, filters, expand/collapse dimensions etc. But these days, right click always give me error as shown in image below. And I am not able to do anything on the grid.
My environment are
SharePoint Server 2013
My machine: Windows 10
SSAS 2016
This problem occurs also on my colleague's computer which has Windows 7 installed. Help please.
A colleague of mind had modified the default master pages, it is when some JavaScript functions got screwed up. I had to revert them back to their initial versions. It worked like a curse broken free.
During the work week, I jump around a lot doing several different things. I don't get to spend dedicated time in Cognos Report Studio. I tend to work on a lot of different stuff all the time. It would be nice if Report Studio offered a way to see the last 20 reports I was working on. This would be similar to how Microsoft Excel keeps track of the most recent spreadsheets that were opened.
So I'm wondering if there is a way to show the last 20 reports that were opened with Report Studio?
You can create special report for it.
Use Cognos audit package and create report based on COGIPF_ACTION table.
Use COGIPF_OPERATION field to filter out only actions you need.
Use COGIPF_TARGET_PATH field to get object.
You even can create URL to open this report in Report Studio.
I've started using Crystal Reports recently. Have been able to create a report and mostly done with it. But suddenly I started to lose any change made inside a textbox object. I edit a textbox, save the report and close it. And then I reopen it to see that the change hasn't remained. I restart the Visual Studio and even the machine but nothing helps. I use VS 2012. Has anyone experienced anything like this?
In the report preview see if the checkbox "Save data in the report" is checked. If so, try unckecking this checkbox. It is causing me some trouble to save the report crashing Visual Studio interface.
In fact I found the reason for the problem. This happens when I try to save the changes while the focus is on the edited object, in this case textbox. But if I click somewhere else (in order to lose focus on the edited textbox) before saving, then the problem gets solved. Happy to have found it.
Welcome to the club :)
Crystal Reports can behave very strangely in some cases. For instance, some times when i edit a report file in Windows XP, it crashes the interface and corrupts the file when i save it. The same problem doesn't appear in Windows 7. However other strange things happen in Windows 7 also.
I would recommend you to
Always apply the latest Service Pack available for the Crystal Reports Engine.
Always check if the asterisk sign disappears from the opened report file when you save it (some times it doesn't when you hit save and it does when you hit save all and vice versa).
Always backup your report files once in a while because to recover a corrupted file is a very hard task.
You can try the following to find out what causes the problem
Create a new blank Windows Forms project, add the same report file there and check if it behaves the same.
Create a new blank report file and check if a change in a field behaves the same way after saving it.
Try it on another OS.
Go to Database | Verify Database and make sure the database is up to date.
Also Go to Database | Show SQL Query and reset the query. Now enter in the Selection Formula again and save.
Updating the SQL will replace the Selection Formula.
Good luck,