I had this issue with Sage 300 2019. PU3 was fine, but PU4 it had this deficiency. (They are now on PU6 and same issue still exists... so it wasn't fixed in the next 2 releases.)

My workaround was to rename UQ66A on the PU4 install directory and copy UQ66A from a PU3 install.

In PU4 there were, apparently, performance improvements, but they broke the component descriptions in the process.

In your case, I would try to find a UQ68A directory from a 2021 install with no product update and see if that works. If it doesn't work, you might have to try jumping back releases... which may get more risky.

Definitely call Sage about this and open a ticket. Hopefully, the more people that call about it, the sooner it will be addressed.

That's poo! I thought PUs carry forward so something that got fixed in a PU3 will be fine in the next versions. I will call Sage on this but hopefully they will see this post and do something about it.

I hate going back and renaming folders for the current version and going back to an older version since we have no idea what was fixed or not.

Thanks for your input!

So I have a case number with Sage: 8008652553.

They have been investigating this since September 2020: KB106947

Joseph K from Sage says: "Development is committed to look into this in March". There is no ETA for a fix at the moment.

Thank you

Dear Diary, 

It has now been a little over 3 months since I opened this case with Sage 300. I chatted with a tech today and lo and behold the case was again closed because "it was not actively been worked on." It is still being checked into by the development team. I am now trying to see how I can escalate this to someone above the chat or the call representative. The client is not impressed and neither am I. *heavy sigh*

Hi Prabha, thanks for reaching out! See that you chatted with support yesterday. I've pulled the call notes and forwarded your comments here onto Sage 300 support management for review and a further push (if possible) on details from the development team looking at the issue reported on KB 109657. Will update you with any news.