Can someone else try this for me?

Go to https://your server/apps/erp/home/#/home?licenseType=CRM

Search ‘Quote’

Right click on the Quote Entry menu item and do ‘Open in new tab’

When the quote landing page opens, find a quote that has been marked quoted.

Open the quote, and press the print icon.

I get a license error

Does this happen to anyone else?

Not happening for me on 24.2.

The strange thing is the ‘open in new tab’ part is critical. It doesn’t happen if I open in in the same window

Ok so what’s even more weird. When I went back to the quote list I got a license error.

Have you tried with holding the control key before clicking the quote entry - its the same as the “open in new tab”

DaveO

Tried that just now, same issue happens.

I made a case, CS0005269675

I wish there was a workaround, this is a real headache for our CRM team

So if you don’t open in new tab, it doesn’t give the error? You can right click on a tab and “duplicate”. Maybe that’s a workaround?

Ok, I can can consistently get this to happen now. I cleared browser data for our Epicor instance and logged back into /apps/erp/home/#/home?licenseType=CRM. Now it’s consistently happenig.

If I login into /Apps/ERP/Home/#/home first or at all then go to /apps/erp/home/#/home?licenseType=CRM it seems fine.

1 Like

And session management still shows you consuming CRM and not a full license if you do that?

I just tried that. I tried duplicating the home screen and then opening quote entry, and then I tried duplicating the ‘good’ quote entry tab and both of them had the error.

Good idea though

1 Like

Yeah. I am consuming a CRM license and a full license when I do that. Not ideal either.

2 Likes

This causes a bunch of other license and access errors when you go back to the full client. So I wouldn’t recommend switching between CRM and full. I had to logout and clear browser data to fix it. I couldn’t open any menu item in the full client when I went back.

Epicor says they cannot reproduce on my environment with the login I gave them…

3 Likes

But yet we all can. :poop:

1 Like

I thought maybe it was a user account thing, so I used the one I gave them and I still got the error, on a fresh browser

2 Likes

Come On Wow GIF by BrownSugarApp

I’m dealing with the same thing on a different ticket. They admitted they could reproduce it but it was quote “fixed” by development. So they said it couldn’t be an issue anymore. But they admit it still happens. Now the ticket has been open for 50-60 some days with no action by Epicor.

4 Likes

Third support rep is the charm. Reproduced and submitted to development.. Lets hope there is a fix before classic sunset..

3 Likes