# I'm on 2024.1.10... How about y'all?

**URL:** <https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190>\
**Category:** Kinetic ERP\
**Created:** [August 24, 2024, 1:33pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190 "2024-08-24T13:33:16Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![SteveFossey](https://www.epiusers.help/user_avatar/www.epiusers.help/stevefossey/32/19220_2.png) [@SteveFossey](https://www.epiusers.help/u/SteveFossey)\
**Post date:** [August 28, 2024, 1:57am UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/41 "2024-08-28T01:57:28Z")

</div>

> [@LoganS](#):
>
> load them in as external DLL’s or create my own api to load in

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.

---

<div class="post-metadata">

**Author:** ![Espa](https://www.epiusers.help/letter_avatar_proxy/v4/letter/e/50afbb/32.png) [@Espa](https://www.epiusers.help/u/Espa)\
**Post date:** [August 29, 2024, 3:31pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/42 "2024-08-29T15:31:15Z")

</div>

@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?

---

<div class="post-metadata">

**Author:** ![spaceage](https://www.epiusers.help/user_avatar/www.epiusers.help/spaceage/32/49289_2.png) [@spaceage](https://www.epiusers.help/u/spaceage)\
**Post date:** [August 29, 2024, 3:44pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/43 "2024-08-29T15:44:07Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Espa](https://www.epiusers.help/letter_avatar_proxy/v4/letter/e/50afbb/32.png) [@Espa](https://www.epiusers.help/u/Espa)\
**Post date:** [August 29, 2024, 6:22pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/44 "2024-08-29T18:22:08Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![spaceage](https://www.epiusers.help/user_avatar/www.epiusers.help/spaceage/32/49289_2.png) [@spaceage](https://www.epiusers.help/u/spaceage)\
**Post date:** [August 29, 2024, 6:49pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/45 "2024-08-29T18:49:17Z")

</div>

I was told the same thing

---

<div class="post-metadata">

**Author:** ![Espa](https://www.epiusers.help/letter_avatar_proxy/v4/letter/e/50afbb/32.png) [@Espa](https://www.epiusers.help/u/Espa)\
**Post date:** [August 29, 2024, 8:09pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/46 "2024-08-29T20:09:31Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![Alamdar](https://www.epiusers.help/user_avatar/www.epiusers.help/alamdar/32/52187_2.png) [@Alamdar](https://www.epiusers.help/u/Alamdar)\
**Post date:** [August 29, 2024, 8:13pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/47 "2024-08-29T20:13:49Z")

</div>

For us, almost all dashboards have the refreshing and saving issue!

---

<div class="post-metadata">

**Author:** ![dcamlin](https://www.epiusers.help/user_avatar/www.epiusers.help/dcamlin/32/57759_2.png) [@dcamlin](https://www.epiusers.help/u/dcamlin)\
**Post date:** [August 29, 2024, 8:35pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/48 "2024-08-29T20:35:42Z")

</div>

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!

:dumpster_fire:

---

<div class="post-metadata">

**Author:** ![josephp](https://www.epiusers.help/user_avatar/www.epiusers.help/josephp/32/77784_2.png) [@josephp](https://www.epiusers.help/u/josephp)\
**Post date:** [August 29, 2024, 8:39pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/49 "2024-08-29T20:39:35Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Espa](https://www.epiusers.help/letter_avatar_proxy/v4/letter/e/50afbb/32.png) [@Espa](https://www.epiusers.help/u/Espa)\
**Post date:** [August 29, 2024, 8:53pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/50 "2024-08-29T20:53:08Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![spaceage](https://www.epiusers.help/user_avatar/www.epiusers.help/spaceage/32/49289_2.png) [@spaceage](https://www.epiusers.help/u/spaceage)\
**Post date:** [August 29, 2024, 8:56pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/51 "2024-08-29T20:56:01Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![LoganS](https://www.epiusers.help/user_avatar/www.epiusers.help/logans/32/53356_2.png) [@LoganS](https://www.epiusers.help/u/LoganS)\
**Post date:** [August 29, 2024, 9:15pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/52 "2024-08-29T21:15:23Z")

</div>

I miss my comfort feature, I hope they add something to mass delete and mass insert into the In statement of table criteria.

> **Video Proof**
>

---

<div class="post-metadata">

**Author:** ![Ernie](https://www.epiusers.help/user_avatar/www.epiusers.help/ernie/32/69401_2.png) [@Ernie](https://www.epiusers.help/u/Ernie)\
**Post date:** [August 30, 2024, 1:07pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/53 "2024-08-30T13:07:06Z")

</div>

There’s an Epicor Idea for that… vote!

[https://epicor.ideas.aha.io/ideas/KIN-I-5118](https://epicor.ideas.aha.io/ideas/KIN-I-5118)

---

<div class="post-metadata">

**Author:** ![Olga](https://www.epiusers.help/letter_avatar_proxy/v4/letter/o/57b2e6/32.png) [@Olga](https://www.epiusers.help/u/Olga)\
**Post date:** [August 30, 2024, 2:27pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/54 "2024-08-30T14:27:03Z")

</div>

Did you report it? It is better to do if you want something implemented.

---

<div class="post-metadata">

**Author:** ![markdamen](https://www.epiusers.help/user_avatar/www.epiusers.help/markdamen/32/54917_2.png) [@markdamen](https://www.epiusers.help/u/markdamen)\
**Post date:** [September 3, 2024, 12:22pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/55 "2024-09-03T12:22:07Z")

</div>

Are you logging in using Epicor Identity?

---

<div class="post-metadata">

**Author:** ![LoganS](https://www.epiusers.help/user_avatar/www.epiusers.help/logans/32/53356_2.png) [@LoganS](https://www.epiusers.help/u/LoganS)\
**Post date:** [September 5, 2024, 2:21pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/56 "2024-09-05T14:21:16Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![cmulford](https://www.epiusers.help/user_avatar/www.epiusers.help/cmulford/32/60940_2.png) [@cmulford](https://www.epiusers.help/u/cmulford)\
**Post date:** [September 5, 2024, 2:57pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/57 "2024-09-05T14:57:49Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Mark\_Wonsil](https://www.epiusers.help/user_avatar/www.epiusers.help/mark_wonsil/32/51594_2.png) [@Mark\_Wonsil](https://www.epiusers.help/u/Mark_Wonsil)\
**Post date:** [September 5, 2024, 3:07pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/58 "2024-09-05T15:07:07Z")

</div>

> [@cmulford](#):
>
> “Warning this BAQ takes (xxx) seconds to execute in SQL, this may result in performance degradation”

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?

---

<div class="post-metadata">

**Author:** ![Chris\_Conn](https://www.epiusers.help/user_avatar/www.epiusers.help/chris_conn/32/93797_2.png) [@Chris\_Conn](https://www.epiusers.help/u/Chris_Conn)\
**Post date:** [September 5, 2024, 3:14pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/59 "2024-09-05T15:14:04Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![cmulford](https://www.epiusers.help/user_avatar/www.epiusers.help/cmulford/32/60940_2.png) [@cmulford](https://www.epiusers.help/u/cmulford)\
**Post date:** [September 5, 2024, 4:37pm UTC](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190/60 "2024-09-05T16:37:54Z")

</div>

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.

[Previous page](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190.md?page=2)

[Next page](https://www.epiusers.help/t/im-on-2024-1-10-how-about-yall/118190.md?page=4)
