Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics NAV (Archived)

Job Value Entry

(0) ShareShare
ReportReport
Posted on by Microsoft Employee

Hi everyone, 

Can you help me how can i resolved this issue, i can't post documents with regards to job module in NAV 2009, this error always prompt.

 

 

Error message when you post a job journal or a purchase order or purchase invoice that is linked to a job in Microsoft Dynamics NAV 2009 Service Pack 1: "You do not have permission to modify records in the Value Entry table"

 

Hope you can help me how to resolved this issue, this issue has can cause of the delay of our process since we encountered this issue last 2015.

 

 

Thanks & Regards.

 

Katana.

 

*This post is locked for comments

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Job Value Entry

    Thanks Sir Vishal, i can now post the job journal modules.

    Katana

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Job Value Entry

    Hi Katana,

    Just go through follow steps (second image). This should resolve your problem.

    To resolve this problem, in the Permissions property of the "Job Jnl.-Post Line" codeunit (1012), add table 5802 with Read permission and Modify permission as follows:

    Object ID Object 5802

    Name Value Entry

    Read Permission Yes

    Insert Permission No

    Modify Permission Yes

    Delete Permission No

    Regards,

    Vishal Salot

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Job Value Entry

    Hi Sir Vishal, this is the full resolution, am i going to download hotfix? Or i can be add the procedure you send?

    RESOLUTION

    Hotfix information

    A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV 2009 service pack or the next Microsoft Dynamics NAV version that contains this hotfix.

    Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

    Installation information

    Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

    Note Before you install this hotfix, verify that all Microsoft Navision client users are logged off the system. This includes Microsoft Navision Application Services (NAS) client users. You should be the only client user who is logged on when you implement this hotfix.

    To implement this hotfix, you must have a developer license.

    We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:

    The Modify permission for the object that you will be changing.

    The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.

    Note You do not have to have rights to the data stores unless you have to perform data repair.

    Code changes

    Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.

    To resolve this problem, in the Permissions property of the "Job Jnl.-Post Line" codeunit (1012), add table 5802 with Read permission and Modify permission as follows:

    Object ID Object 5802

    Name Value Entry

    Read Permission Yes

    Insert Permission No

    Modify Permission Yes

    Delete Permission No

    Thanks & regards.

    Katana

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Job Value Entry

    Hi Sir Vishal,

    You mean i need to add the first image in the design table of the codeunit 1012?

    Thanks & Regards,

    Katana.

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Job Value Entry

    Hi Katana,

    As mentioned, you would require to go to Codeunit 1012 in design mode > Properties (Shift + F4), Permission property.

    Give the required permission for value entry table here.

    Please note, you need developer license to modify the coduenit and to add the required permission related to value entry in the same.

    Once you add the required permission in Codeunit 1012, you should not be able to face any issue.

    7065.2.JPG

    As system is modifying ValueEntry table in CU 1012, you need to add this permission here.

    This is bug and has been resolved in later product releases.

    7065.2.JPG

    Hope this helps.

    Best Regards,

    Vishal Salot

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Job Value Entry

    Hi Sir,

    I can't debug this because the this is our clients database we can't access for now, this issue was emailed to us, but they have resolutions, i'm a newbie in NAV so i can't understand some of the resolutions, hope you can help me for me to understand the resolution, please see below.

    We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:

    The Modify permission for the object that you will be changing.

    The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.

    Note You do not have to have rights to the data stores unless you have to perform data repair.

    Code changes

    Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.

    To resolve this problem, in the Permissions property of the "Job Jnl.-Post Line" codeunit (1012), add table 5802 with Read permission and Modify permission as follows:

    Object ID Object: 5802

    Name: Value Entry

    Read Permission: Yes

    Insert Permission:No

    Modify Permission:Yes

    Delete Permission: No

    I cant understand the stated "The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object."

    I already simulate as a super user in other database, but i can't change it.

    Hope you can help me.

    Thanks & Regards.

    Katana

  • Suggested answer
    Alexander Ermakov Profile Picture
    Alexander Ermakov 28,094 on at
    RE: Job Value Entry

    Most likely it is a limitation of the role that you use to post entries. Normally, typical license should allow to do this. Check if you can make the same posting under SUPER user role. If positive, investigate the role settings for problematic user.

  • Suggested answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Job Value Entry

    Hi,

    Can you please debug and tell me, in which screen / form / codeunit / table, you are getting this error?

    There could be two reasons to this.

    1. License or User Role permission issue -

    > Get the updated license or given the necessary rights to the users.

    2. Could be customization in the module, which is causing this issue.

    >In this case, you can give the required permission at object level to resolve the issue (Via developer license).

    How do you normally resolve this issue otherwise, when you faced last time?

    Hope this helps.

    Best Regards,

    Vishal Salot

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Congratulations 2024 Spotlight Honorees

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December

Congratulations to our December super stars! 🥳

Start Your Super User Journey

Join the ranks of our community heros! 🦹

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,711 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,458 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans