I implemented it on 10.2 and also used it on 11.0. Yes, not sure how useful this will be after 2026.1 as you will no longer be able to make configurator inspection plans.
Even if you are not pushing this to SSRS, there is a lot you need to do just to get it into a BAQ. There are no native connections between the tables and you need to create them yourself.
Yeah we know in the newest version the inspection plan is automatically made. I just found this as an interesting possible solution for reusing attributes since that was our main concern. Need to consider if this is worth the implementation time just to help us with that one aspect.
Hi John,
I got a new question for you. As I am creating these inspection forms I need to document who filled them out in a BAQ that I will turn into a dashboard. I noticed that InspResults holds EmpID but in my testing it is always blank. I can do some advanced customization to pull it in at some point along the journey but wanted to check with you.
Do you know if EmpID populates in InspResults if a certain order of operations is done, and if Epicor never set it up did you do any work around for this to have employee ID in the dataset?
I cannot remember. I believe it was either 1 of 2 things. I either made one of the Inspection Attributes to hold the inspector or that might only populate if you use the Inspection Results Entry screen.