Report Viewer issue when renders report vs export to PDF

Posted by: grapecity on 27 May 2020, 12:13 am EST

    • Post Options:
    • Link

    Posted 27 May 2020, 12:13 am EST - Updated 3 October 2022, 4:15 pm EST

    I have Wijmo Report Viewer to render flxr reports. The same reports are being used in a Winforms application using Flex Report Viewer.

    Here is the image of the report rendered in Flex Report in Winforms. (winform_flexviewer.jpg).

    The problem is that in the Wijmo Report Viewer some parts of the reports looks ugly as you can see in the image (wijmo_reportviewer.jpg).

    If you export the to PDF then it looks good as you can see in the image. (wijmo_pdfexport.jpg)

    So I dont knwo what could be the issue, dont know if could be due to fonts or something but is a big issue that we need to solve.

    Any clue on how to fix this?

  • Posted 27 May 2020, 12:14 am EST - Updated 3 October 2022, 1:49 pm EST

    Last two images are inverted.

  • Posted 27 May 2020, 11:03 am EST

    Im using Tahoma font. Could this be the issue?

  • Posted 28 May 2020, 3:59 am EST

    Hi,

    We do not think that font could be an issue. Can you provide us with the FlexReport you are using or any other simple report will also work as long as the issue occurs in whichever report you provide? If you can, then it will be easier for us to investigate this issue.

    If you cannot share the report publicly, then I could create a case on our SupportOne Portal(http://supportone.componentone.com/) where your data can only be seen by the engineers and not general public.

    Regards,

    Ashwin

  • Posted 29 May 2020, 10:59 pm EST - Updated 3 October 2022, 4:15 pm EST

    Sure here is a sample report with the issue.

    Here is how it looks in the ReportViewer:

    Here is how it looks when is exported:

    Also attached is the .flxr report file.

    Thanks and let us know how can we fix this.

  • Posted 29 May 2020, 11:00 pm EST

    Attached is the zip file with the .flxr report file.PreAuthorization.zip

  • Posted 1 June 2020, 8:17 am EST

    Hi,

    It seems that this issue is fixed in the latest C1WebApi version. Can you please upgrade web api to the 4.5.20201.253 and try again?

    ~regards

  • Posted 1 June 2020, 10:56 am EST - Updated 3 October 2022, 1:49 pm EST

    Can confirm that this is resolved with the upgrade of the version. THanks a lot Ashwin for your always awesome support.

  • Posted 2 June 2020, 12:07 am EST

    I am glad to be able to help. Let us know in case you have any further issues.

    ~regards

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels