I don't think is something we need from that table but because something was not done correctly during the update of the secific DB. I recall a report we used to run during the upgrade for this table. So maybe I missed that step and now hits on the DB.
As far as I can understand, by running the form once the primary key is created and no longer returns the error.
This can also be a license issue. A developers license may look for setup records that usually are not needed when the client's license is used. If you then insert the record you may get read permission errors if the client's license is used and that module is not included in the license.
Comments
Try running form 5919 from the object designer, then close the form. After that, try posting again.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
That worked on my testing DB. Time to check on the actual DB.
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
As far as I can understand, by running the form once the primary key is created and no longer returns the error.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book