We have a pilot version of kinetic and I have a customization that is not working because I have an epibinding to fields that are not available. I have regenerated the data model twice and ran any conversions that were pending. Not sure where to turn to now. This works fine in 10.2.700 but not 2024.2.Examples below.
This is Kinetic and a image of porview: my ud fields are not there.
Yes. My theory is that inspection processing uses a view (porView) instead of the actual table and in creation of the view they forgot (or ignored) the possibility of custom fields.
Support told me that my custom field would show up in the oprView but by the time the came back with that I had already re-worked the process so we didn’t need the custom fields and didn’t bother checking to see if they were right. At some point I lose the will to fight each and every ticket.
I guess what I’m saying is glance in the OprView table and see if it’s there, otherwise I wish you better luck than I had.