I’m working on my first customization layer for Part using an erp-combo-box and am bewildered.
I added a combo-box to the newly created and saved layer, did not configure it with anything other than customizing the ID and Label Text. Preview – the combo is there as expected.
I don’t have a solution yet, but I have determined that the problem is that 2025.2.16 is picky about UD column names – and it’s not just the Kinetic UX.
I started down the Kinetic customization path because I had 2 combo boxes that disappeared from my classic customization when I updated to 2025.2. The customization conversion didn’t flag an issue and I didn’t catch it until today. We’ve been live on 2025.2 for about 2 weeks now.
After failing to get them functional in classic – even if I created new combos for the columns, I gave up and switched to Kinetic UX.
It didn’t occur to me until a short time ago that the problem might be deeper than just the Kinetic UX. That Kinetic combo that disappeared, came right back when I changed the binding to a different UD field.
If I bind the control to either of the 2 UD fields that “disappeared” from my classic customization, the control disappears in the Kinetic UX too. There’s nothing that I consider strange about the UD fields. They are “Brand_c” and “Logo_c”.
For good measure, I’ve regenerated the DB and that didn’t help.
Root cause found. The 2 UD Fields in question had “Hidden by Default” set in the UD configuration. Somewhere between 2023.2 and 2025.2, the behavior of Kinetic customizations was changed so that the “Hidden by Default” switch is interpreted as “Hidden”.