Kinetic Tracing - Persistent Trace to File - is that possible?

Forgive my ignorance, but in all the labs at insights for the past couple years all the tracing we have done has been using dev tools where you trace what you’re doing at the moment…

I have a client who is reporting an issue with quickship where she is freighting a shipment, the label comes out, then a second later a second label pops out with a different tracking number, but all the same shipment details as the first one. So… our user goes and looks in UPS and it turns out the first label/shipment was voided… but she never unfreighted or voided anything, she just hit freight…

So… I’m trying to trace out what’s happening, where the void/unfreight calls are coming from and I was thinking a client trace would be the way to go since this is sporadic and not happening every shipment. I know how to do it in classic and classic writes to a file which is nice… but is there a way to make this happen for Kinetic forms and tracing their rest calls?

I am cloudily remembering an option to log it to a server file, but alas, I can’t quite remember.

In short, is there a way to log kinetic client trace to file?

Thanks,

Utah

1 Like

I have not done it yet, but you can set up traces on the User File now.

I think the UI is only in the Classic Client.

You use the Tracing sheet to activate client tracing for the current user account. Through this feature, you can control when a client trace log runs for a specific user and then turn off this log when you no longer need it.

The tracing log is a tool that has several uses. Web service developers can use this log to see what business logic calls are made when users launch a specific function; for example, the business logic calls made when a user enters a new customer record. Custom programmers can use this log to fine-tune their customized applications. Epicor Technical Support may also ask you to turn on this log to help them track performance issues or other technical issues.

3 Likes

Phil Hartman Yes GIF

This isn’t going to trace from the web though.

@hkeric.wci and Kevin and @jkane, we use a smart client and launch kinetic screens. If I enable the client trace from the classic screen, it will then log anything she’s doing in the kinetic customer shipment screen yeah?

nope

That’s the basis of my question then… how do I log what she’s doing in her kinetic screen all day long? Or at least for a reasonable period of time to try and track down this issue?

1 Like

Perhaps have to use via Chrome/Edge and run the DevTools? Make sure she doesn’t close the tabs though.

1 Like

chrome://tracing/

1 Like

Warning, never used it, might be Pandora’s box.

doctor who GIF

1 Like

Tried that in Edge and it referred to use the new Perfetto UI. Could be another Pandora’s Box.

Spoilers!

1 Like

I see, yeah, just launch it in different window and then have her minimize it and keep that screen open.

My question is, if she closes the kinetic screen for some reason, she’s probably going to have to re-launch the debug console yeah?

1 Like

I usually scan the ServerLogs which technically trace as well, but it wouldnt show client side attempts that don’t make it.

You can give Capture, debug and mock your Electron app's HTTP traffic a try and simply pick Chrome.

2 Likes

Thanks Haso, I was already looking at server logs just now :wink:

Didn’t have them set to capture enough time though and the event that I need is too far in the past.

I’ll try and work with the server logs and try that tool after that.

1 Like