Permission Problem
matias_jaure
Member Posts: 157
Hi Everybody,
We have a permission problem on the license that should be used on production.
When we post an order, we insert some records in G/L Entry for deferral porpouses, this is a customization made by us. With our developer license we have no problems, but with the license that our client buught it gave us an error: "there is no permission to insert in G/L Entry table" or something like that.
Any idea how tyo aboid it? or any idea what we should ask the client to buy??
Thanks!!
Matias
We have a permission problem on the license that should be used on production.
When we post an order, we insert some records in G/L Entry for deferral porpouses, this is a customization made by us. With our developer license we have no problems, but with the license that our client buught it gave us an error: "there is no permission to insert in G/L Entry table" or something like that.
Any idea how tyo aboid it? or any idea what we should ask the client to buy??
Thanks!!
Matias
0
Comments
-
If you are writing directly to the G/L Entry table (which is not recommended) then you will have to give the object that contains the code, permission to write to the G/L Entry table. Look to the properties of this object to set these permissions.0
-
matias_jaure wrote:Hi Everybody,
We have a permission problem on the license that should be used on production.
When we post an order, we insert some records in G/L Entry for deferral porpouses, this is a customization made by us. With our developer license we have no problems, but with the license that our client buught it gave us an error: "there is no permission to insert in G/L Entry table" or something like that.
Any idea how tyo aboid it? or any idea what we should ask the client to buy??
Thanks!!
Matias
For me it is signal, that you are creating the entries in your own code, instead to fill the G/L Journal by code and post the line through CU12!!! Please, look at it, do it in correct way, or you can mess up the main table of whole system! [-X0 -
shrekut wrote:If you are writing directly to the G/L Entry table (which is not recommended) then you will have to give the object that contains the code, permission to write to the G/L Entry table. Look to the properties of this object to set these permissions.
Thank you! I do it and works!.. we create several records on G/L entry to deferral porpuses, it's the only way we have to do that, thank again0 -
What is the reason you cannot use C12?matias_jaure wrote:Thank you! I do it and works!.. we create several records on G/L entry to deferral porpuses, it's the only way we have to do that, thank again
Like Kine wrote, you should always use C12 to write into the G/L entry table. At least this way you are sure it is done correctly. Also in future versions.Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0 -
Creating journal lines and posting those lines is the way the entire application works. Please listen to us and redesign this process. Do not write G/L entries directly.0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 610 NAV Courses, Exams & Certification
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 251 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions


