Hi there,
Relative novice to Kinetic and I have a scenario I need to resolve that I’m not sure how to approach. Basically my company is going to have information that we were planning on storing in an external table that we could then access through a function to insert customer-specific data into an operation, however I’m not sure how or if there’s a way to access external SQL data this way. Has anyone else figured out how to resolve this?
Alternatively is there any way to create new user defined tables that the system can use? Thank you.
You can create an External Business Activity Query that can ready data from an external source. There are also a ton of User Defined Tables that exist for you to “claim” for your own use and then you can also add your own User Defined Fields to those tables.
The simplest option is likely the UD Tables/UD Fields combination as those are easily available to all the customization/automation tools that Epicor provides. Each of the UD tables already comes with a canned UD Table xx Entry form that you can also modify to suit for adding/updating/deleting the UD records.
Thank you for the reply! After doing some looking around I noticed the UD tables I believe you’re talking about. Just to make sure I’m not accidentally looking in the wrong place, these would be, for example, the ICE.UD01, UD02, etc, tables correct?
I’ll try to explain it a little more in detail for the sake of good explanation.
In our pre-Kinetic system we had a customization in place that stored customer specific notes for operations. That way when an operation was added to a part for a customer, those notes would be added in with it. So Customer “ABC” could have specific notes for when operation 123 is used or when operation 456 is used. But Customer “XYZ” could have different notes for operation 123. I’m investigating trying to find a way to replicate this in Kinetic and I believe the UD route that Chad mentioned, along with some custom functions/events, could probably achieve what I need.
So if your “user defined data” is super simple, like ID and Description simple…You could also use User Codes and not have to mess around with UD Tables.
For User Codes you define a Code Type and then the individual does under each Code Type. There’s not much substance here, but if you just need an ID code and a Description, this could also potentially handle what you are doing.
Ah, but if you need a multi key solution like: OpCode and Customer, (or Customer, Part, PartRev, OpCode) you might need to go the UD Table route where you have 5 keys for your record.
