2024.2.4 - Material tags suddenly default to printing portrait?

Upgraded to 2024.2.4 over the weekend and now the default checkbox for printing material tags (to client printer) is portrait – the landscape checkbox is unchecked. The material tags are designed in SSRS as landscape and historically the “Landscape” checkbox had defaulted as checked.

It doesn’t appear that this screen is using my local printer preferences, and, at a glance, it doesn’t appear I can use Application Studio to default the checkbox for this report. Anyone seeing similar issues and/or have a solution?

1 Like

See if this helps

2 Likes

Laura,

I am having this issue too. I put in a ticket for Epicor support, since this was working in 2024.1. They told me what you already said that the report defaults to what the RDL file is made as. Like you, I have the report as landscape, but it still defaults to portrait.

I was also told that I have to go to company maintenance > reports and make sure that paper size is set to use RDL default, but that did not fix this at all.

There was a bug in the RDD where the subassemblies weren’t printing correct information. I wonder if they fixed that.

1 Like

Good to know this isn’t just a problem we are seeing! I know there are plenty of other bugs that came with 2024.2.4 so this is probably low on the priority list, but here’s hoping they resolve it in one of the next patches.

@Taylor_L did Epicor Support accept your ticket as an issue? We recently upgraded to 2024.2.12 and are seeing this issue now. We have some custom reports where the RDL is defined landscape. Prior to this upgrade the Kinetic Report menus printed out landscape but now they are printing portrait…when sending directly to a printer. Classic Report menu prints the same RDL as landscape. We can use Print Preview and then send to printer as a workaround but users really don’t like these extra steps…especially when it worked fine until recently.

It has been a while, but I am pretty sure that epicor said that this wont be fixed because this is happening in the desktop client and not the browser.

1 Like

I was afraid of that as I just completed a test on the Web Browser and discovered it is not an issue there. Of course I had to download an updated version of Edge Agent first which requires me to get off of our network in order to download and then use an Admin user account to install. I haven’t rolled out the browser to our users yet…they have enough issues with the Kinetic menus :sob: The Edge Agent install is one of our hold ups to rolling the browser out but I do plan to start with a select group soon.