We previously added a UD field for LaborEntryMethod.to the Classic version of Operation.
We’ve recently upgraded to Kinetic and found that Epicor have now added DefaultLaborEntryMethod to OpMaster table out of the box.
This is great as I don’t need to create a customised layer for the Kinetic application. But as we will be running Classic and Kinetic side by side for a while I’m trying to update our Classic customisation and add the out of the box OpMaster.DefaultLaborEntryMethod to replace our UD field.
When I look at the Kinetic application I’m struggling to understand where it is getting the static list from to populate the drop down list?
As Text = display and Value = value I expected to see these records under List but there is nothing there:
I have been trying to add a combo box in Classic for DefaultLaborEntryMethod without any luck. I’m thinking the business object is not retrieving the values for the field in Classic??
I can’t really help on the classic end, but in app studio, the “List” option would be utilized in scenarios where you want to build a static List of drop down options to populate your combo box. In this case, it’s not necessary.
It’s getting a predefined list from the OpMaster table… and the DefaultLaborEntryMethod field.
Assuming classic can access that table/ field (don’t see why it couldn’t) i would just have to play around with those epiCombo settings to find the right combination of settings. But again, i do apologize in not much help on that side of things. Especially considering I’m not in front of my PC to experiment with you.
I would search the forum for other examples of classic combo set ups.
Ok thanks for that confirmation - I did see guides regarding building your own combo / static list. I expected that might be the answer…Epicor stores those values somewhere that we can’t see. I was really just digging around here to try and help me setup things on the Classic side.
Yeah, can definitely see the table/field in Classic. I have actually just done a similar change for another application (PartClass) but it was a checkbox field rather than a combo with drop down list. Will keep searching to see what I can find.
Ok I figured it out and it was simple. All I had to do was change the EpiBinding to the new table/field value. I kept the EpiCombo pointing to UserCodes business object (the list I had created previously for our UD field) to populate the drop down list. Whatever generates the drop down list for the field in Kinetic doesn’t seem to work in Classic. I was over complicating things by trying to replicate how Kinetic generated the drop down list.