There are lots of examples on this site. The FIRST thing one always needs to do, is to capture a trace of what standard Kinetic does. This tells you what gets called in which order. People who avoid the trace will waste hours/days/weeks trying to “figure it out” on their own.
Here are two tools to check out:
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.
[image]
[Kinetic UX Trace Utility]
We have submitted to Chrome for Web Store approval but that may take a few weeks. In the meant…
So we’ve been working on a little utility to help parse the Epicor Trace Files and make development a little easer.
Here is a walk through
[Epicor Trace Parser / Differ]
Below is some more info on how to use it. The most important but is how you setup your Trace. Your trace should be setup as shown
[image]
I know we (most of us) normally say “Track Changes Only” but this is big bold lie, it shows us what has changed in the data-set (even stuff we haven’t manually changed). This t…
Once you know how Kinetic does it, you duplicate those calls in the function. Again, lots of examples here on EpiUsers.help .
Searching “function joboper” yields:
Looking for some help here…
I am working on a function to adjust the ProdStandard value on a job operation.
The function takes 4 input parameters: JobNum, AssemblySeq, OprSeq, and Adjustment. (Where adjustment is the number of hours to increase/decrease the estimated hours on a job operation)
The function is purely code, using the CallService method to call the BO methods. I performed the desired steps in the UI and kept the Trace Log. The code attempts to replicate those same method calls.
C…
3 Likes