Difference between EpiCombo and EpiUltraCombo dropdowns

Hi guys,

What’s the difference between the EpiCombo and EpiUltraCombo dropdown boxes? The help topic “Controls List” basically has the same for both, but says EpiCombo is faster since it doesn’t need an adapter. Where should I use each? I’ve read a few posts where folks use the EpiCombo for User Code dropdowns, which is where I’ll be using this (to record the reason why a quote was lost). Figured I’d learn why, and not just follow rote memorization :slight_smile: Thanks!

Controls List Help Topic:

EpiCombo

Click this tool to create a drop down list. Drop down lists display a selected option in the main field, but when users click the down arrow button, they may select another available option from the list. With this tool selected, click and drag your mouse pointer over the form. A drop down list appears with its resizing handles. Release your mouse button to drop the list onto the form.

When configuring EpiCombo, the EpiBOName property has to be fully resolved with the namespace for the service, based on the schema to which the selected table belongs. For example:

  • Ice:BO:UserCodes
  • Erp:BO:OrderHed

If you are binding the EpiCombo to a Numeric column, you need to define some additional control properties so the data displays in the numeric format you need. You first select the Numeric column (

.) for the EpiBinding property; this links (binds) the database column from which the EpiCombo pulls data for display.

You next indicate the datasource this EpiCombo will use to populate the drop-down list. First select the ValueMember property and enter the name. You also set the DisplayMember property to either Null or the same name. If a numeric format is defined for the selected EpiBinding column, this format displays by default. However if a numeric format is not defined or you need to create a custom format, launch Extended Properties Maintenance . Select the

. you used for the EpiBinding and enter a custom format in the Format field such as the “->>>,>>>,>>9.99” value. The custom format you entered displays on this drop-down list during run time.

Tip: This control is derived from the UltraCombo control. Because of this, this EpiControl retrieves data from a data object without using an adapter; this improves the performance of your customization.

EpiUltraCombo

Click this tool to create a drop down list. Drop down lists display a selected option in the main field, but when users click the down arrow button, they may select another available option from the list. With this tool selected, click and drag your mouse pointer over the form. A drop down list appears with its resizing handles. Release your mouse button to drop the list onto the form.

You can bind an UltraCombo box to a Data Source/Data Field and also select it to retrieve data from a specific table. You select these options on the Control Properties for the combo box.

Another control, the Combo , is derived from the UltraCombo. Use the Combo control to create drop down lists that use less system memory than UltraCombo lists.

If I’m pulling data from a standard Epicor table, I will use EpiCombo 95% of the time. It doesn’t require any code and is lightweight to the system. If I need a list I generate dynamically then I use an EpiUltraCombo.
Don’t forget BAQCombo too. I don’t use it as much because it requires things outside my customization, but it works very well. You can even filter (search for EpiBinding)!

@Jason_Woods would know for sure but is there a restriction to EpiCombo when using User Codes or do they work with EpiUltraCombos too? I seem to recall never being able to get Ultra’s to work with User Codes through the Extended Properties.

UserCodes are best done in EpiCombos ALWAYS (unless you need to use a Like filter…)
They can work in EpiUltraCombo, but again, why code it?
Short answer: If you are using a BO, don’t use EpiUltraCombo.

2 Likes