Edit Sales Shipment Header Table

LibertyMountain
Member Posts: 94
We have a custom field in Sales Shipment Header called "Picking Mistakes". Initially, we had some issues populating the field. As a result, some of the records have bad data in the "Picking Mistakes" field. I want to correct the data, so we have accurate historical performance Reports. But, when I try to change the value, I'm told that I cann't edit the table.
If I try via Object Designer > Table 110 > Run > edit a "Picking Mistakes" value > I get the error: "Sales Shipment Header cannot be modified in this form."
If I try programmatically, I'm told I don't have necessary permissions.
I have SUPER access. Version is 3.71, running on Windows Server 2003.
If I try via Object Designer > Table 110 > Run > edit a "Picking Mistakes" value > I get the error: "Sales Shipment Header cannot be modified in this form."
If I try programmatically, I'm told I don't have necessary permissions.
I have SUPER access. Version is 3.71, running on Windows Server 2003.
0
Comments
-
Table Sales Shipment Header it's a protected table. Normal customer license can't change data in that table.0
-
Yes you need to be able to modify codeunit 3910
-
To correct the bad data, put your code in a function and put the function
in any codeunit.
Just call "codeunit.yourfunction" when you want to update the records.0 -
1) Superuser isn't gonna be able to do it.
2) 391-Codeunit-(Shipment Header - Edit) is the logical place for accessing the Shipment Header.
You need to have someone do this...
OnRun(VAR Rec : Record "Sales Shipment Header")SalesShptHeader := Rec; SalesShptHeader.LOCKTABLE; SalesShptHeader.FIND; // << Shipping Change SalesShptHeader."Picking Mistakes" := "Picking Mistakes"; SalesShptHeader.MODIFY; Rec := SalesShptHeader;
0 -
smkolsoft wrote:To correct the bad data, put your code in a function and put the function
in any codeunit.
Just call "codeunit.yourfunction" when you want to update the records.
In some tables end user license can't modify even if there is a codeunit in customer license (50 000 – 99 999). To end customers modify those tables you must add those functions to specific code units has Alex Chow said.0 -
0
-
What?! Didn't even realized I was involved in this conversation.
Anywho, without the application builder and the solution developer license granule, you won't be able to modify codeunits. Especially codeunits that modifies data in a protected table.Confessions of a Dynamics NAV Consultant = my blog
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book0 -
Alex Chow wrote:What?! Didn't even realized I was involved in this conversation.
Anywho, without the application builder and the solution developer license granule, you won't be able to modify codeunits. Especially codeunits that modifies data in a protected table.
sorry, #-o
Correction, Savatage0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions