Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Modifying Cust. Ledger Entry and G/L Entry?
Andy_Smith
Member Posts: 31
NAV2013
I have a client that had several weeks of transactions post with bad "Description" fields for Cust. Ledger Entries, which in turn fed to the same field in G/L Entries. Table 36 Posting descriptions were changed to an uninformative and uniform "Entry <Document No.>" instead of the default of the document type and the document no.. We've fixed the table 36 issue, but now want to clean up the existing entries in the CLE and GL.
I'm aware that any modification of G/L Entry is generally frowned upon, and would not attempt to do so for anything other than resetting bad descriptions to the default behavior.
I've created a processing report to scan for Customer ledger entries that have the bogus description and first change the G/L entries associated with it, and then the Customer ledger entry, but when I test it on a single CLE entry, I receive an error: "You do not have the following permissions on TableData G/L Entry: Modify". I do have SUPER role, and I do have full DBO permissions on this database.
Is this a permission that is unavailable due to concerns of modifying the G/L, and if so, what would be the recommended recourse for the client to fix these descriptions? I can modify other tables without issue and wasn't aware of any hard locked tables existing, but wasn't sure if this is a new feature in 2013?
I have a client that had several weeks of transactions post with bad "Description" fields for Cust. Ledger Entries, which in turn fed to the same field in G/L Entries. Table 36 Posting descriptions were changed to an uninformative and uniform "Entry <Document No.>" instead of the default of the document type and the document no.. We've fixed the table 36 issue, but now want to clean up the existing entries in the CLE and GL.
I'm aware that any modification of G/L Entry is generally frowned upon, and would not attempt to do so for anything other than resetting bad descriptions to the default behavior.
I've created a processing report to scan for Customer ledger entries that have the bogus description and first change the G/L entries associated with it, and then the Customer ledger entry, but when I test it on a single CLE entry, I receive an error: "You do not have the following permissions on TableData G/L Entry: Modify". I do have SUPER role, and I do have full DBO permissions on this database.
Is this a permission that is unavailable due to concerns of modifying the G/L, and if so, what would be the recommended recourse for the client to fix these descriptions? I can modify other tables without issue and wasn't aware of any hard locked tables existing, but wasn't sure if this is a new feature in 2013?
0
Answers
This is not something new. Been this way for a very long time.
Brian is correct, with an end user license you have to give the object extra permissions.
Look at codeunit Cust. Entry-Edit (103) as an example.
I guess programmers never ran into these issues in the past where you would just run the report with your dev-license. Now we have the situation where changing the license on a customers live database is less simple.
Good luck.