It's here.... 2026.1.100 Feedback Thread (Behave 🤣 )

Kinetic ERP
162

Do you have any update on this? I was attached to this PRB a few days ago when doing UAT. Our Quote Form, Sales Order Acknowledgement, Purchase Order Form, and AR Invoice are erroring out during testing, all with similar errors mentioning “Invalid attempt to call MetaData when reader is closed.” or “Invalid attempt to call FieldCount when reader is closed.” errors.

I reached out to someone I met at Insights about the number of open PRBs we have, she looked at the PRB today and it has been updated to show ‘Resolved in 2026.100.7’. I sure hope so, that’s only a few days before Production receives the update.

163

That just means “All 10,000” or truly All if you do what @dcamlin said about Query Executing Settings.

Well, scratch that. Learned something new today. You can type whatever in that field and it will exceed the 10K limit. :exploding_head:

image

image

164

It did, I saw a tip here recently which is my favourite new thing F12 right click on the refresh select Empty cache and hard refresh, super quick fix :grinning_face:

165

I arrived this morning to 8 emails telling us nothing new apparently fixed in 2026.100.7 but when do we get that or is there a work around in APR I have asked the question awaiting response, It’s EOFY and we cant email invoices :frowning:

166

Looks like you can’t break down releases on sales order entry anymore, just throws an unexpected error.

Doesn’t matter how you go about trying either. So that’s with EpicCare to look at…

167

Update is that the fix is scheduled for 2026.100.7 which should be available in CMP starting 29th June. Workaround suggested removing all variable inserted fields in APR. I am a bit rusty in APR as we set it up ages ago and haven’t touched since, but the email address is a variable inserted field right? so how is that a possible work around, please tell me this is not correct.

168

What do you mean?

169

That is correct, you have to use variables to populate the Email To field (among others).

I can’t even get ours to Route to our Dev ECM site, you have to use Variables to populate the Identify Table Record in the Add DocStar Attachment

image
image1176×644 44 KB

170

Can add a line to a sales order just fine. Say for 200 units. We then break those 200 units down into actual releases, i.e. instances of 20 per release. That functionality appears to be broken. They’ve confirmed it, so just waiting on a resolution now…

171

What’s the error?

172

We are running into an issue where a layer will just randomly eat one of its own dataviews after its populate / get event runs. We can see the empty dataview before the get, trigger the get with no error, and then poof its gone.

Any one else seeing this?

173

Not seeing any issue adding multiple releases:

image
image925×791 45.6 KB

What did they confirm? Are there any nuances to how you’re doing this? It seems to work for me.

174

I know that’s what’s tripping me up…I haven’t heard anything about this yet.

175

Has anyone been able to test if this effects BPM’s that fire similar logic?

176

I can confirm that our basic BPMs that email, even with Variables, do fire and email out.

image
image1456×1041 47.2 KB

image
image1543×589 74.6 KB

These do not Route documents. That seems to be the underlying culprit for us with our errors and failures.

177

They’ve come back to me. Looks like there’s a BPM on the OrderRel table which is causing it. It’s one that Epicor Professional Services put in when we went live years ago, so that’s a nice fun one to sort!

178

New twist on our Customer Shipment Entry problem PRB0318806. It doesn’t seem to be recognizing security at the user level for site access anymore.

Have a user that’s only got access to one of our sites…logged in, CSEntry shows packs from all four sites…and allowed his profile to update an existing pack from a different site (including checking/unchecking the “Shipped” checkbox and updating the Ship Date).

179

email only fails when it is asynchronous.

180

I was about to say, I’m pretty sure you have a customization hiding out!

181

Exactly, it’s when we find out if we get to keep the magic smoke in the PC. :slightly_smiling_face: