Posted Invoice Update - UD Field

Kinetic ERP
1

I’m attempting to add an editable field to the AR Posted Invoice Update application, that is linked to a UD Column on InvcHead. The UD field is not related to Epicor’s posting logic, it is only for reporting purposes.

So far, the editor I have added is always disabled. I tried copying one of the built-in Row Rules that controls the disabled state of a standard editable field (TermsCode), and editing it to reference my UD field. The field is still always disabled.

PIUPD_DisableTerms

image
image1840×963 49 KB

PIUPD_DisableExpectedPaymentDate_c (My copy)

image
image1843×961 53.2 KB

Has anyone done this before? What step am I missing?

2

I think this is already reported as an enhancement, if not you can report it.

I think the issue is from the rowrule that disabled the entire InvcHead except for a few fields, so UD fields are also disabled.

3

Thank you. In the meantime, I will use a TransView column for the UI and update my UD field with a function call.

4

The pattern is that there is usually a row disable, and it’s partially editable so you can add extra columns to the “except” list. I haven’t tested it because I don’t have a UD field, but seems to exist in the right format in this UI app too:

image
image1635×656 45.8 KB

  1. Locate the InvcHead disable row rule
  2. Observe that it is partially editable
  3. Note the small overlapped text titled “except these columns”.
  4. Add your UD field to the list
  5. Save
5

Thanks Mark,

This looked like it was going to be a slam dunk, but it doesn’t have any effect on the disabled state of the fields. I’m wondering if this is one of those ‘black box’ items that you can’t actually affect via Application Studio alone.

I tried this approach with both my UD fields, and also a standard field (FOB). In both cases, the fields stay disabled. So I’m not sure if that Row Rule is effective at all.

6

Apparently, this issue was fixed between 2025.2 and 2026.100

The Row Rule does work in my 2026 test environment, so this is the solution, just not in our live environment at its current 2025.2 version.

Thanks again @markdamen