After looking further into this, the xml data refers to the field name and the guid related to the object on the screen, so you need to tie them together to be able to do the mapping… Looking at xxxdef unless the specific classic form has a custom and the field is customised then you can’t see it from the database side… You would need some more in depth tools or the source to be able to create the map in the first place… That’s my take, but I think a few people clueyer than myself may have other thoughts.
1 Like
Not to kindle said dumpster fire… but @klincecum crying over this made me laugh!
6 Likes
Thank you forum for remining me that no, this really hasn’t been answered yet.
Can more people please vote for Randy’s newly-created idea about fixing this?
https://epicor.ideas.aha.io/ideas/KIN-I-6194
Not sure how many people need to vote to spur some real action on this vs. hand waving.
7 Likes
I suspect the main hurdle is subscription and pricing.
As long as Epicor depends on SQL Server, SSRS shows up for free. I think the threshold is one decision maker who has the power to assume all risk of committing to a subscription expense with a new vendor that disrupts an existing feature, who assumes zero consequences by doing nothing.
2 Likes
Ok ok take your SSRS complaining to another thread. This one is for complaining about field help. I can’t believe on 36 people care about fixing field help. Come on people! Log In - Epicor Identity
6 Likes
Make that 37!
This is perfect!
Sigh.
5 Likes
You have my vote. Wild that customers have to garner votes for fixing major regressions.
8 Likes
I am thinking that they just need to run cursor over the codebase to build the update program… A good intern project me thinks.
5 Likes
Ok, I’ve created a new Idea to bring field help to classic parity. It has already been linked it a few times in this thread too.
Thanks for your votes everyone!
3 Likes
Or maybe just use Prism 
4 Likes
One could argue that they bring back the documents@epicor.com email address and slap it in the field help and just bypass the whole Epicor idea process…
1 Like
Whatever it takes to get Kinetic up to Classic parity before you guys take Classic away.
7 Likes
Prism can help bring it up to classic parity!
3 Likes
Don’t you have to pay for Prism? So parity is give Epicor more money?
5 Likes
Interesting idea, but is Prism going to have access to the source so it can translate the classic fuel guids back to the XML then also relate that to the Kinetic fields.
But then again having a Prism Field Help Agent, might be a nice pet little project for Marketing, Insights 2026 perhaps 
Prism does not address the On-prem elephant. In all seriousness this is a real issue and I admire the commitment to improving the content, the first step should be make it match with the classic, then revisit, or make it a parallel project.
This should have been addressed when field help first got added to the Kinetic UI… It is not a finger pointing exercise and we don’t need excuses, we just need action!
7 Likes
Maybe Epicor will give on-prem customers a discount on maintenance, since we can’t have Prism! 
3 Likes
For every prism, there will be an equal and opposite refraction.
I think the Model Context Protocol is going to make it possible to run agents locally. It’s only been around since November and it’s taking over the AI world.
5 Likes
Apologies everyone I am not trying to ruffle feathers…
3 Likes
3 Likes