Without converting the BAQ Grid to a dashboard, how can I permanently set the column widths in the BAQ Grid so they remain as narrow as possible while keeping text visible? For some reason whenever I manually adjust them and click ‘save layout’ it doesn’t save the column widths.
Thanks!
What do you mean by this? Are you talking about within BAQ Designer?
The last time I asked this, the main recommendation I got was to move it to a dashboard. I’m curious if there is a way that doesn’t involve moving them to a dashboard.
Where are you displaying the BAQ on the Homepage?
Okay… Homepage.
That’s what we were trying to figure out. Where you were viewing the BAQ grids.
I just tested and threw this BAQ grid up on a Homepage tab, and after saving layouts, it seems to have stuck as a personalization.
I jumped around in tabs, closed my browser, logged out and back in… seems to have saved the personalization okay (2024.2.7).
Not sure why yours won’t stick.
For anyone out there having this issue, Epicare confirmed that it’s related to PRB0290482. Hoping they resolve it soon!
New to Epicor…what does PRB0290482 mean?
PRB’s are “problems” that have been acknowledged by EpiCare.
So, if you see a PRB number, you can go into EpiCare and look under “Other Resources” and “Problem Repository”:
You should see historical problems that have been tracked. Turn on your filters and you can search for a specific number:
A lot of times, you may enter a case with EpiCare and they’ll link your case to an existing PRB number… meaning the issue was already reported by one or more other users. So, instead of tracking each case individually, they’ll say it has been accepted and linked to PRB number 1234567, and you can track progress there.
If you’re ever facing a problem, you can try to search the PRB descriptions with keywords and see if anybody else had previously reported the same issue. And if so, there may be comments from development on if/when the solution may be expected.
Along those lines, if you’re ever facing a problem, you can also search KB (“Knowledge Base”) Articles on EpiCare to see if your particular problem was solved in the past. The KB Articles will show steps required to work through particular issues.
I bring this up mainly because you were asking about “PRB” numbers… but you may also see users here, or even Epicor Support refer to “KB” numbers/articles. And that’s where you can track those down as well.
That all being said, even if you find an existing PRB that is the same, or related, to your issue… it is still best to log your case. The more users who report the issue, the more emphasis/resources they may place on getting it fixed.
Hate to say its a “squeaky-wheel” policy, but… 100 companies reporting an issue, you would assume, would get more attention than 1 company.
So, if you’re seeing the same issue as above, you could enter a case and include the above PRB number as a reference in your case description. They’ll review the PRB and, if they agree that it appears to be the same problem, they’ll link your case to the PRB as well.
… kinda like adding your name to a Class Action (just without the hope of any kind of payout).
the payout would be less frustration! 
