Anybody else having issues with comboboxes in 2025.2.16 (or there abouts)?
I am building a dashboard (UD101 Entry) and adding a combobox for Resource.
I have Combobox #1 set up for the ResourceGrpID. No issues. (Bound to UD101A.DtlResourceGrpID_c)
The second Combobox should return Resources within the selected ResourceGrp. (Bound to UD101A.DtlResourceID_c)
These are the settings used in Epicor’s stock Time Entry for the same combobox:
When I add the Filters Param setting to my combobox (ALL settings are just like the existing/working combo from Time Entry), I get an error in debugger and the combobox is disabled.
I see the following in Dev Tools:
This also happened in a previous effort to use a Job Assembly combobox, again, copying the settings exactly from an Epicor stock combobox. Adding the Filters Params resulted in the same forEach is not a function error.
I worked around that issue using a BAQ instead. But I am now seeing the same problem again and I just wanted to see if anybody else has seen/reported this.
I did just enter a case… but I’m at a standstill at this point (unless I want to again, create a BAQ just to return resources which I shouldn’t have to do).
Pre-existing comboboxes set up the same way have no issues.
~*~
Exploring with ChatGPT:
That error strongly points to Filters Params being in the wrong shape/type.
a.forEach is not a function usually means Epicor expected an array/list of filter param objects, but it received a plain string/object instead.
getFiltersParams(a) expects a to be an array, because it immediately does: a.forEach(...)
But it is currently probably being stored as one plain string
~*~
… again, just wanted to see if anybody else has seen issues with this lately.
