Skip to main content

Hello,

(We are on 23R1.6 in our environments.) We have a quick report that pulls invoice data, we can export this data from the quick report page, completely fine. We encounter no issues and the excel formatting is perfect.

 

The issue we are encountering though, is when scheduling this report via scheduled reports, and having it emailed to our users, we notice that the method used to export the data onto an excel sheet adds an extra space and a new line character before the field values for all columns/rows. We cannot fix this on our end since these characters are added after the data is pulled from the quick report.

 

Has anyone else encountered this issue?

 

Thanks,
Bryan

Hello @ChanakaAmarasekara

I was told you would be the best person to ask about this. If you could provide any information regarding this issue, it would be very much appreciated.

I checked the application messages for the attached report and it also appears on that excel, so I’m assuming there is an issue with the formatting of data onto the excel sheet rather than an issue with the email.

We also notice that the conditions in the quick report are not being applied to the emailed report, but only the exported one when viewing it as an end user, for example if I pull all fields and say where invoice_id=1000, the quick report will only return invoice 1000, but when scheduling the report, it pulls all invoices, very odd!

Again, any and all input would be greatly appreciated.

Thanks,
Bryan

Hello, 

We are experiencing same issue with format of report when it is sent by mail.All columns are with one extra row before  field values for all columns/rows.

Is there any solution for this, it is not possible to fix this every time after mail is received.

IFS CLOUD version 23 R 2

I just encountered the same issue in 23R1 SU17.  Has anyone found a solution other than running the report manually instead of scheduling it?

Hi All,

We have encountered a few cases related to this issue, and some fixes have already been implemented. However, it appears that further investigation is needed in the latest environment. I will provide updates on this thread as more information becomes available.

Thanks, Ashen.  I did open a support case CS0316979 in the meantime.

Reply


Terms & ConditionsCookie settings