Reports with Barcodes/QR codes are not able to print

Hi,

We have the same problem

regards

Daniel

Hello,

This is not a solution, but quick workaround: you can change QR code in report layout to DataMatrix:

Regards,
Andrij

Hi, we have the same problem. What is your Framework service update?

Hi ​@InfJurajC,
We are currently on 24.2.7. Apparently other customers have also reported it and right now it looks like its a bug.
 

Hi @Himasha Abeywickrama,

Thanks. Yes, it does look like a bug. We have several customers experiencing this issue, and it is likely related to the Framework 24.2.7 update. Everything seems to be fine in previous versions.

Hi,

We’re experiencing this same error while trying to print/preview any report with a barcode & a QR code  in the report. This now in IFS Cloud 23R2 SU5  Placing only barcodes in the report will work. Problem is with the QR code.  Once this is in the report it will give the error. 

Framework 23.2.19 here. 

Any idea? 

Regards, 

Nilla

It looks like recent delivery installations have upgraded framework to the newest version that is afected by this problem.

Hi ​@knepiosko ,

Yes, it is as you say. Everyone should be warned not to install delivery on Production, or not to update the framework during installation.

There are already several cases on IFS reporting this problem.

I created ticket for this issue but support is expecting an example… It seems we have to wait for totally diaster

Hi,
it should be possible to give installer particular helm version to install.
I’ve tried one modify yaml and remove ~ (tilda) character to install particular version, but it was ignored and latest version was installed anyway.
It is probably also part of delivery or maybe muiltiple places, so maybe it has to be used as cmd parameter to override all occurance.

https://docs.ifs.com/techdocs/25r1/070_remote_deploy/010_installing_fresh_system/200_installing_ifs_cloud/035_ifs_cloud_ifsinstaller/030_installation_parameters/#general_parameters:~:text=master%2Dchart%20%22-,chartVersion,-Normally%20only%20used

Hi, 

We raised a ticket too.

• We had a delivery to PROD on wed June 18th - (framework 23.2.18)  and we don’t experience the issue there with the QR’s. 
• On the 20th of June we had our next delivery to TST - (framework 23.2.19) and there we experienced the issue with the QR’s.  
• and on the 25th we delivered to CFG - (framework 23.2.19) and have there also the same issue. 

Between the 18th and the 20th of June this error occurred. 

I am working with a 24R2 and we also got the same error, we notice somethign interesting, the same layout and same report doesnot error in Buildplace. So we think its something to do with our “Remote” deployment of our Useplaces.

But if you order a new build place environment you may experience the issue. During our testing, we also noticed that the same report is working fine in build place environment. Hence, we tried to order a new environment for further testing and ended up with the same error in new build place environment.

 Latest IFS response:

This issue has also been identified in the 25R1 track.

The R&D product team has acknowledged it as a defect and is currently working on a fix with the highest priority. We will share further updates shortly.

As for the CSM and LE warnings and other release related processes, the release management teams will review them based on input from the R&D team.

Hi Everyone,

This has been identified as a core bug and reported to RnD for a permanent fix

/Shanaka
 

H all, 

We’re all stuck with deliveries right due to this.

Do any of you have an update on the issue? Any reply from RnD?

BR Nilla

Hello,

this issue still exists in 25.1.1. version on a customer’s MIG environment.

Best regards,
  Stefan

This seems to be a big problem.It should display as a warning  in build place or SNOW so then we can avoid delivery installations. 

Best Regards,
Wasana

2025-07-01 15:22:44:

Your case is currently being investigated by an expert within the Research & Development team. This process usually takes up to 5 days but can be longer in some cases. During this period, we will determine whether your case is accepted as a core product error or if an alternative resolution can be provided.

 

unbelievable… 

2025-07-02 12:07:03 CEST - System

New comment from JIRA Integration (by IFS R&D): Hi,

We have now accepted your case as most likely a core product error. We will begin designing the fix which will be released in accordance with our support policy.

Hi,

See below info we got the 27th of June: 

This has been identified as a core bug and reported to RnD. we are waiting for a permanent fix
https://ifsdev.atlassian.net/browse/DUXZREP-1964
 

I wanted to make you all aware of this KBA on this issue, it will continue to be updated as the solution evolves  https://ifsworld.service-now.com/csm?id=kb_article_view&sysparm_article=KB0086493

Assuming a customer proceed with Option 2 in the Knowledge article, could someone confirm if this fix and the change will be retained after a customer upgrades to 25R1 SU1, or will it be overridden, therefore requires to apply the fix again?

Hi,
what does this mean? Is error corrected and is safe to install deliveries without any additional steps.
Or this will be possible after next SU only and it is still broken and manuall deployment editation is required even for installations after correction?

BR
Filip