Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.6K 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
- 280 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 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
[Unsolved] Compound primary key for Item table
Forza
Member Posts: 64
Anybody have any idea how to setup compound key in Navision? Particularly for Item No.? For instance, making No. + No. 2 to be a compound primary key. How will this affect other tables like sales line, item journal, etc?
Any help will be appreciated. Thanks a million.
Any help will be appreciated. Thanks a million.
0
Comments
What are you trying to acheive?
My scenerio is:_
In production order routing line I wanted to create a modified routing for rework operation. System says for filtering correctly that rework boolean field should be part of the primary key. We cant change the primary key of the production order routing line table.
Let me explain you better:_
On production order of Item A is released with operation 1,2,3,4 and 5.
At the time of posting of the operation 4 it has to be sent back to operation 2 or 1.
At the time of posting output from output journal the user tick the boolean and a routing line is created and machine center/work center Task List is updated.
Now the particular work center/machine center user can post the output against that particular production order when the rework boolean is ticked on the output journal.
Please advice!!
This solution was suggested to avoid any double entry of the product/material combination and also to make it easier to create an item. Looking up to a list of pre-defined list is always better than remembering where you left off.
Any other way anyone can think of that will help solve this situation? Thanks a million.
It sound like a wrong table relation design. You can only relate a field to an external primary key.
Something like relate a Manufacturer field -> Item."Manufacturer Code". The correct relation is Manufacturer field -> "Manufacturer.Code"
Eto
Been there, done that. This option can't work for two reasons.
1. The cost and price for the different product/material combination must be different. Selling price is not a big issue, but cost is. Because we bought them at different price from the vendor. Without segregating them in the item code level, it is almost impossible to set different cost for different product/material combination.
2. The Variant Code will be used for finishing color, since all of them is the same cost and selling price.
Thanks for the suggestion though, Mauddib. But I need a more innovative approach. Anyone out there can't help overcome this M::I?
Then hide "No." From the user.
Whenever 2 or 3 are changed you call the code:
VALIDATE("No.", "No. 2"+"No. 3");
So now users can enter their two values but it always gets fed back into the primary key as one compound value.
Will have to ensure the lengths of 2 and 3 can only be a sum total of 20 characters though.
If selli9ng price is not the big issue then you can use Varients. The cost of the item and Varient will be done on the basis of costing method selected on the item card and this is working fine.