In vendor ledger entries can't edit "on hold"

This field can be used when a vendor ledger has been invoiced and you run the Suggest Vendor Payments batch job.

You can use the field to determine whether the posted vendor entry will be included in the payment suggestion.

Before posting, you can fill in the field with your initials or any other code to indicate that the vendor entry should wait for approval before a payment is made.

If the field is filled in, the entry will not be included when you run the Suggest Vendor Payments batch job. The field will show that the entry is waiting for approval. If the field is empty, the entry will be included in the payment suggestion.

The field can be filled in from the following fields:

If the entry was posted from a journal line, the contents of the field are copied from the On Hold field on the journal line.

If the entry was posted from an order, invoice or credit memo, the contents of the field are copied from the On Hold field on the purchase header.

Depending on how you get to the page you may need to click "Edit List" because the initial view may not be editable. Seeing as you say it's editable when you change to a Worksheet type page I believe this is the most likely issue.

You can not edit directly data in Customer/Vendor ledger table, as customer grade license does not allow for this. It never did.

But some ledger fields, including On Hold, can be updated using codeunit 103 for Customer Ledger Entry or 113 for Vendor Ledger Entry.

Look into Page 25 or 29, into OnModifyRecord trigger, to see how this is achieved,

What do you mean by saying "when running table 21/25 from the developer environment the field "On Hold" is not editable."

License does not include field level permissions. Customer license does not allow to modify a record Customer/Vendor ledger entry table as a whole, but it never influences editability of a single field. I would expect that all of the fields can be modified when a T21/25 is run from the object Object Designer (with the exception of the ones having the Editable property set to No), but N AV would prevent you to write changes to the database

If the field is grayed out when when you run the table from Object Designer it means that Editable property on the table field is set to No.

The license only controls writeability of changes to the database, not the appearance of the record/field.

Is this standard unmodified code in all test cases? Have you checked your user role permissions? Maybe none of your roles have the Indirect modify permission to the T21/T25 ?

This is a bug in a few versions of NAV 2018 - you need to add Table 25 (read & modify) to the "Permissions" property of Page 29 Vendor Ledger Entries

mgn wrote: »

Thanks Kishorm, this works.
Out of curiousity: is it a bug in one of the binaries?
In older version of NAV the pages 21 and 29 do not have these permissions set either: the objects have the same properties!?

I believe they changed the binaries to make the UI more intuitive, i.e. disable the "Edit" if you did not have rights to Modify the table. However they then should have also set the "Permission" property on these pages so that the UI knows that the page is editable (it's done via calling a Codeunit in the OnModify trigger of the page).

P.S. Please mark my previous response as having answered the question (easier for others to the see the solution).