I had to do this with SQLClient when going from 2021 to 2022.
Used nuget to build a dotnet app that uses SQLClient, pulled the dll from the bin folder, plunked it in my externals folder. Of course, it’s not automatically updated, which carries a risk.
@spaceage We are seeing customer layers not loading. I opened a case with support and they indicated that a few other customers are experiencing this same issue. It’s causing issues for us when we configure products in CPQ and come back to a base screen and the UD fields aren’t mapped. Do you think this is cache related?
I do think it’s cache related. I typically try a refresh, if that doesn’t work, a hard refresh (SHIFT + refresh), and if that doesn’t work, use the browser tools to clear cache. Usually a hard reload works, but I had an incident today where it didn’t and I had to completely clean the browser cache.
Thank you – I’ve added this feedback to my support ticket. Support is telling me they cannot enter a PRB because it cannot be recreated on demand.
I was told the same thing
Ok, we may have found something to recreate the issue on demand. If we click the Customer tile on the home screen, and then back home, then click on another tile that has a custom layer, it opens in base. So Customer, home, Quote entry, we see base. If I start quote entry to Order entry, I see my custom layers. Basically, if you start navigation from the Customer tile, we are seeing base every time. Could you see if you’re experiencing the same?
For us, almost all dashboards have the refreshing and saving issue!
Hmmm.
Start >
Customer from widget: Opens w/ Layers
Home
Quote from widget: Opens base
Home
Order from widget: Opens base
Home
Customer (again) from widget: Opens w/ Layers
Test 2:
Quote from widget: Opens base… REFRESH (layers turn on)
Home
Order from widget: Opens base
… so refreshing one, didn’t seem to have any impact on the other.
Home
Quote from widget: Opens w/ Layers (remembered my recent refresh)
Home
Quote from MENU: Opens Base! 
Home
Quote from widget: Opens w/ Layers (remembered my recent refresh)
Order from widget: Opens Base
Home
Order from MENU: Opens w/ Layers
Home
Order from widget (again): Opens w/ Layers!! WTH!! Cannot nail down a pattern!
YES! us too! I have had a ticket since the update came out and escalated this and we are still dealing with this - we were supposed to have another face to face with an Epicor tech today and they were a no show… another add on to the ticket… I’ll let you know when we know something.
Ok, now I don’t know! I can seem to recreate it following this below. I did not refresh at all during this test below. When we navigated to apps using the menu tree, the issue does not seem as persistent.
Customer from widget: Opens w/ Layers OR Opens Base
Home
Order from widget: Opens base
Home
Job Entry from widget (no layers on this app): Opens base
Home
Order from widget: Opens w/ Layers
Else, I’ll be damned, you found a repeatable pattern!
I open Customer from a Home Page tile, it loads in the correct layer after selecting a record to view. If I click the Home icon in the left-most menu to go back Home, then open a record in Order Entry (which has a custom layer), the base version opens with no layer applied. It’s easy for me to tell, as I have (2) additional panel-card grids on the layer that do not load in base.
I’m going to update my ticket right now! Thanks for sharing!
I miss my comfort feature, I hope they add something to mass delete and mass insert into the In statement of table criteria.
There’s an Epicor Idea for that… vote!
Did you report it? It is better to do if you want something implemented.
Are you logging in using Epicor Identity?
ReportSelCriteria folder in report server was missing - we moved from 2022.2.14 to 2024.1.0->.5->.10 so maybe this issue won’t exist if you moved more frequently than us.
It seemed any report that was in SQL blobs wherever they’re stored worked fine but the lingering SSRS reports had issues, such as our General Ledger report.
I copied in our old 2022.2.14 version but a little weary about that.
Didn’t find that as an issue for anyone else on here after some searching so wonder if it’s an isolated case for us.
Anyone cloud users seeing query timeout issues or warnings since 2024.1? We have been getting this on several queries “Warning this BAQ takes (xxx) seconds to execute in SQL, this may result in performance degradation”. If we call from Rest to load our BI tool it fails. I don’t recall seeing this one before. None of the queries had any issues prior to the upgrade.
I have a ticket in and they acknowledge it’s an issue but, they have been slow to respond on it.
I’m wondering if Epicor is working on the “noisy neighbor” problem by informing customers of BAQs that may be, well, noisy.
What do these BAQs do? Is it possible to refactor them to be more performant?
Just updated our testing env to 24.1.11 yesterday and we saw what appeared to be the old version layout until we cleared the cache.
They are heavy hitters, a lot of order details getting pulled into a Qlik datastore for historical analysis and the like. Always looking a ways to optimize but they just require a lot of tables and sub queries. Nothing I’ve done in the BAQ parameters has made any difference.
They have changed something in the DB structure as we never had issues before the upgrade weekend. We are running at about an 80-85% fail rate on them now and never noticed an issue before. Both Pilot and Live are seeing the same issue now that we are on 2024.1.