Missing Part Description on Kinetic form

Browser weirdness - not the first time.

Our Part Description is not (visibly) displaying the data.
The data is there. We can see it load in the calls. If we click the field and drag out we get an indication the proper data is there.

So its just not displaying.

This only occurs on Part Tracker (not Part Entry). It only happens in Chrome, not Edge.

The same issue occurs on a base form.

Anybody else ran into this? Epicor says talk to Chrome. I suspect Chrome will tell me to talk to the website provider (Epicor).

I am tempted to write a browser extension to correct the issue as I assume its CSS related.

2 Likes

I’m seeing this in method tracker. This is happening on 2 users that i am aware of. They are also using Chrome. It think it is with the field as it has a text box and revision number, and part number field all tied together.

1 Like

Same issue here, only in the browser…but only for a specific user :thinking:

1 Like

Ours started as specific user. Then it magically disappeared for a week. Now its back for that user and 10+ others.

It’s definitely CSS.

Here’s what I did to see the data in browser console:

const element = document.getElementById('EpTextBox391');

// Verify we have the right element
console.log(element);

element.style.border = '2px solid red';
element.style.backgroundColor = 'yellow';
element.style.color = 'black';
element.style.filter = 'none';

image

SPECIFICALLY THE
ISSUE IS THE STYLE FILTER:
grayscale(0.1)

element.style.filter = ‘none’; //resolves the issue

2 Likes

8 Likes

Thanks @Chris_Conn , can you report your findings to support?

Yes we are creating a ticket.

Here’s a proof of Conncept browser extension.
Link should be good for 7 days.

Use at you own risk, blah blah.

Unzip to a folder YOURFOLDER.
Open extensions in Chrome.
Click developer top right.
Load unpacked - select YOURFOLDER.
Load part entry (or add your page if you added as directed below).
Win.

It’s chatty in console, but you can see it work.

Currently only works against PartEntry. You can add any additional targets in the array at the top of content.js
const patterns = result.urlPatterns || [‘Erp.UI.PartEntry’];
ie. const patterns = result.urlPatterns || [‘Erp.UI.PartEntry’,‘Erp.UI.JobEntry’];

Or open the extension (bomb icon), add a new pattern.
image

1 Like

Awesome work! Thanks! Keep us posted if you get a PRB

Supposedly fixed in 2024.2.14

1 Like

this is what I was told too.
“I was able to find out this is a known issue that is addressed as problem record PRB0295390 and is fixed in version 2024.2.14.
You will get the fix on the next cloud update which should be 2025.1. in the meantime will need to use Edge or Firefox.”

2 Likes