For all you wild ones supporting an integration via API... what's a good standard for logging?

The way I would do it probably wouldn’t void my warranty, but they would at least look down upon
it.

I would like to know what you are referring to if you can find it.

And as for @hkeric.wci , just in case people don’t get my slang, I meant he’s a smart cookie.

I am going to try and find it on the forum if possible but I am not sure it’s here.

Not sure which one, but I’ve seen people call Stored Procedures in BAQs. We often times make our BAQs “Updatable” and then use the Advanced BPM functionality of the BAQs for additional code, hence the BAQ starts to behave like a Function then.

1 Like

Aw thanks, im taking a break from the forums… because all I can say about Epicor lately is all negative stuff, so better to stay quiet. I’ve said enough about their poor quality assurance, they will blacklist me. :slight_smile: Be back soon. No offense if I dont reply fast. Been a wild 4 months, personally and professionally.

6 Likes

thanks for this suggestion.

I have been logging in a UD table and it’s been super nice. have resolved 100% of the errors using the data I am logging.

Almost up to our 100th LTL shipment through the API integration with freightview. this is only like 10% of our shipments to start, but it’s going well so far.

Sweet, will you finish mine?

1 Like

Hahaha I am still working through this and trying to add more functionality!

star-wars-meme

@klincecum it was this that I was thinking of. Not voiding anything: