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
Pattern identification issue
Brimstar
Member Posts: 14
I'm working on mapping out a new set of functionality my company needs in NAV. Most of the aspects in the additional requirements fit into certain patterns easily, but my problems comes from a subset of the data that shapes up to be like master data that has a need for maintaining a revision number and revision history.
Quick explanation:
We have a document that is created by our quality department under specific circumstances. It indicates that when we sell part A to customer B we must do X, Y, and Z. X, Y, and Z are defined as processes 1, 2, and 3 in a code list by our quality department.
The bit of data I'm looking at is how we define those codes, called QC codes currently. Considering I'm calling it a document obviously that's a document pattern with the codes being attached as lines. The codes feel like they should be master data, but they must also be maintained as revisions. Entirely possible the code could be updated but historical documents would still reference the older version. What's the best method for this? Is there another pattern I should be considering?
Gut reaction is that do the main characteristics of the QC code that can't change based on versions using the master data pattern and carefully review what can change and place those fields into the rules pattern for the data that has to have a revision maintained since a combination of the master data and this additional data controls what should appear on the main document treating it like the pricing tables.
Overall I'm still new to the idea of designing a whole new section within NAV, having mostly done minor code adjustments in NAV over the last couple years. Just finished reading Mark's book on this subject and this project seems like a good place to start putting this into practice.
Quick explanation:
We have a document that is created by our quality department under specific circumstances. It indicates that when we sell part A to customer B we must do X, Y, and Z. X, Y, and Z are defined as processes 1, 2, and 3 in a code list by our quality department.
The bit of data I'm looking at is how we define those codes, called QC codes currently. Considering I'm calling it a document obviously that's a document pattern with the codes being attached as lines. The codes feel like they should be master data, but they must also be maintained as revisions. Entirely possible the code could be updated but historical documents would still reference the older version. What's the best method for this? Is there another pattern I should be considering?
Gut reaction is that do the main characteristics of the QC code that can't change based on versions using the master data pattern and carefully review what can change and place those fields into the rules pattern for the data that has to have a revision maintained since a combination of the master data and this additional data controls what should appear on the main document treating it like the pricing tables.
Overall I'm still new to the idea of designing a whole new section within NAV, having mostly done minor code adjustments in NAV over the last couple years. Just finished reading Mark's book on this subject and this project seems like a good place to start putting this into practice.
0
Comments
First of all, thanks for reading the book and your interest in the Patterns.
Patterns are about creating recognisable software. You can have a look at the Sales Header Archive table. This has the document signature but with version numbers.
I will most definately make a note of the versioning pattern and publish it on my blog and possibly the next edition of the book.
Hope this helps.
/Mark