Tracing Options on Kinetic Forms

[SimsTrak (Kevin Simon)]

I’m not sure if I’m just not doing something right, but are you still able to run tracing options when you’re running the Kinetic UX form? Example, I open up Tracing Options, click my usual boxes (Enable Trace Logging, Write Full Dataset, Include Server Trace), then I Clear Log and Apply. When I run something in an application that’s the new Kinetic UX, go back and view my trace log, I get the usual junk about the system monitor, etc - but nothing from the application.

I’ve been working around this by running the classic version of the form and doing my trace. If I’m developing a BPM or Function, the trace is the key tool to knowing what’s happening in the application.

Is it just me?

[hmwillett (Hannah Willett)]

The best is if you use Dev Tools in the browser: How To: Debugging Kinetic (Browser) - Experts’ Corner - Epicor User Help Forum (epiusers.help)

[klincecum (Kevin Lincecum)]

No.

But also yes.

The Kinetic forms don’t go through the same process that does the tracing, even when run from the local client. You’ll have to turn on the eo browser debugging to debug kinetic forms when running from the client.

[klincecum (Kevin Lincecum)]

Same thread, local client info:

How To: Debugging Kinetic (Browser)

I didn’t realize you already wrote this up, saw it as I was replying to another thread. In addition to the Browser Debug, here is additional Client-Side Info, for the sake of information. If you are using Epicor Client You can visit this url in the browser http://localhost:1234/ and get to Chrome Remote Debugging Tools. You can also enable some text file logging as well as change the Remote Debugging port by adding the following to your client .sysconfig under <userSettings> <EOBrowser> …

[tpynepeak (Tim)]

Great answers!

But what what was Epicor thinking. Were they hoping that no one would notice.

[hmwillett (Hannah Willett)]

What’s wrong with it? Works just fine.

[Rick_Bird]

@SimsTrak Something to look out for that I’ve ran into a FEW times, is that the Classic & Kinetic Forms do not ALWAYS call the same methods. Just look out for that.

[Mark_Wonsil]

@Rick_Bird

Classic & Kinetic Forms do not ALWAYS call the same methods

Any new capabilities are only done in Kinetic and are not backported to classic, so the APIs are drifting.

[klincecum (Kevin Lincecum)]

@Mark_Wonsil

the APIs are drifting.

True, but it’s more like they made some convenience methods to work better in the browser.

[TomAlexander]

@hmwillett

Works just fine

Not to mention, it’s so much easier in the browser to just look at the network tab in dev tools.

[tpynepeak (Tim)]

@hmwillett

What’s wrong with it? Works just fine.

Yeah it does and thank you for your posts

I was hoping tat Epicor would get it to work with trace logging and there is no reason they couldn’t do that.

Making things different is an easy way to get grumbling

Still slogging through the uplift of a medium sized company. Anything that works similarly to what I was used to is greatly appreciated.

I’ve hit the tipping point where I think that we can succeed (mostly) but a few items were really touch and go for awhile. Inspections though. That is going to be messy.