Inspection Results Entry throws Object reference not set to an instance of an object when trying to enter results

Whenever we try to enter inspection results we receive the following error

Object reference not set to an instance of an object.

Now I checked the plans, they look good. I can also test the plans through Configuration Entry.

Lastly they were working as of a few days ago. Yesterday evening Epicor updated and the next morning I’m getting flooded with error messages.

I checked Pilot and get the error there as well and those plans were also working.

Anyone run into this? Verison 2023.2.9

we are having the same issue. Have a case open. It has not been resolved. The basic functionalitiy works in kinitic screen, but we notice serial number and serial number matching arent working well in the kinetic version. They said to keep classic , they had a weird workaround in meantime:
from support:
The issue is being caused because of a change where the system is trying to find where part number/part revision and inspection plan ID/inspection plan revision equal each other.
So to work around this you just need to have a Part Number and revision that matches the Inspection Plan and revision you want to use. This part doesn’t need to be used in any way and can be marked inactive and deleted once the fix is delivered.

If a part number already exists that matches the Inspection plan then a revision that matches the Inspection plan needs to be added to the part.

Example:
Inspection plan is called “Inspection Plan For Lift” and has a revision A. Creating a Part Number called “Inspection Plan for Lift” and giving it a revision of A will allow you to enter the inspection results.

If you do not use the part in any it can be deleted once the fix is delivered.

1 Like

Thank you! I can verify this workaround works.

I got the suggestion a few days ago but was waiting on approval to add parts to our system. Our team was worried it might impact job costing and want to do some tests.

We are getting the same issue, our version is 2023.2.9, were you able to solve it?

We worked around it as per Micheles post above.

Specifically:

  1. I created parts with the part number being the same as the inspection plan code.
    I made the parts non quantity bearing.

  2. I created revisions for the parts. The revision number on the part had to match the revision # on the plan - the part revision # did not have to be approved.

I made DMTS to cover this as we had 186 plans. Tested in pilot then got approved to move it to production after Finance looked into the transactions.

good tip about qty bearing, we tested 1 inspection plan in our pilot environments and it’s working, will do the same for the rest of inspections, very thankful!

1 Like