LaborSVC minimum fields for clocking in/out

[it_Heroes (Adam Lisk)]

Hi all,

I am creating my own Blazor application that can be used out in the field for our techs. Long story short, they select a job and then clock in and out which then gets approved the next day. Once its approved, the approvee basically hits send to epicor. I have the UI functionality all working so my last piece is sending the data to epicor. I am messing with the LaborSvc endpoints at the moment hoping someone here can tell me the minimum fields for sending clock in/out data to the laborsvc.

[Mark_Wonsil]

Kinetic Trace Helper Utility 1.0 (Kinetic Web) Chrome Extension

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. V1 Launch 10/31/2023 [image] Here’s a Walk Through of the Functionality in Relase V 1.0 [Kinetic UX Trace Utility] We have submitted to Chrome for Web Store approval but that may take a few weeks. In the meant…

Trace Helper Utility for Epicor ERP 10

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…

And

Rest API Example to Update OpComplete on Job Operation(s)

There is no quick win with this, but I would develop an Epicor function to complete the operation. If you use the tracing functionality in Epicor you should get an idea of the business objects to call and use these in your function. Once you have the function working with whatever parameters you want (jobnum, assembly seq and related operation), then all you need to do is call the function via a Rest call from VS, with the correct authentication, if that is you chosen IDE. If you are very new…

[it_Heroes (Adam Lisk)]

I do have the trace tool and I see the endpoints being called. For example GetNewLaborDtlHed, however that is not in the odata side for LaborSvc of the documentation but the RPC side. RPC from what I understand, you have to supply everything where odata you can supply only a few fields if you can. It’s fine I will figure it out like I did with Parts. Thanks.

[josecgomez]

@it_Heroes

RPC from what I understand, you have to supply everything where odata you can supply only a few fields if you can. It’s fine I will figure it out like I did with Parts

the OData Endpoint uses something called UpdateExt on the RPC side. This BO Function call is not always (I would say seldom) Enough for Most complex Bunsiness Objects.

Doing a trace and following it is the safest bet, you can (and I have) accidentally end up with an incomplete, half broken, and or deleted entitiy if you are unlucky enough to be on the receiving end of a half implemented UpdateExt

For something basic like UDXX, or even Part that might be ok, but for complex BOs like Shipping, Quoting, or Labor… I would stick to the trace.

Note that Epicor itself in both the classic and the new Kinetic Client is still using the RPC Endpoints because there is a TON of business logic within them.

PS: Don’t forget the Before Image that one is gnarly in the Labor BO

As @Mark_Wonsil mentioned before your best be is to write a Server Side function that takes the minimum data you have and then builds the records and calls the proper RCP methods server side.

1. You get to send minimum data on the front end
2. You call the proper BOs and don’t hit a wall
3. You save time by doing most / all the processing server side.