After seeing various discussions around tracing for Kinetic
And seeing how popular the Trace Utility Parser was
@jgiese.wci and I decided to start experimenting with a Chrome extension that would bring back / help with some of that functionality in the Kinetic Universe.
Here’s a Walk Through of the Functionality in Relase V 1.0
We have submitted to Chrome for Web Store approval but that may take a few weeks. In the meantime you can side load here’s the install zip we will update this with a link to chrome store once appoved.
Color me gobsmacked the extension has been approved and published to the Chrome Web Store
Follow regular extension install instructions then, you should then see it in your installed Extensions:
Capture all outgoing and incoming JSON requests from Kinetic Client to Server
Group Requests by Business Object and Method
Generate CURL Equivalent of a Given Request
Import to CURL Command to Postman
Save Trace Dump
Load Trace Dump
Support
If you run into issues have questions or have an idea for a enhancement please reply to this thread and we’ll do the best we can to accommodate.
DISCLAIMER
This isn’t an officially supported Epicor tool it was developed by us for the community and our own use.
We do not transmit any data captured by the extension anywhere outside of your browser. This is strictly for internal testing and tooling and we cannot guarantee that will work, that it won’t break anything. We make no claims at all, use at your own risk we aren’t responsible if this extension eats your children or anything in-between. This is a toy and a tool for us to play.
As @Mark_Wonsil said be careful with these traces they contain your token and everything else SO BE CAREFUL
Known Issues
To enable tracing your development tools needs to be attached at the bottom / right of the page otherwise the host page won’t notice the change.
I don’t think so, the security mechanism around browser extensions explicitly forbids eating children’s (and doing ANYTHING remotely useful thanks a lot Manifest V3)… but just in case… keep them away… Or DONT?.. I guess depending on the desired outcome.
Here’s an idea for a feature that I would find useful. I don’t have the technical skill to evaluate whether it’s possible, or if it has any security implications beyond what most would find acceptable:
On the Request side, make the body of the request editable and able to be resubmitted from within the extension, highlighting the new call in the list so that it’s obvious that it’s a modified call.
AND/OR
On the Request side, add a button that when clicked, takes the user to the Swagger page for the Class/Method in the selected call. On click, copy the body of the original call to the buffer so that when you get to the Swagger page and enter the company and api key, you can just paste the formatted request into the Request Body section and modify/test as needed.
Either implementation would allow a user to troubleshoot API calls more quickly.
that’s part of the new feartures we added you can strip out
