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
- 263 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
Decoding a Dynamics 2015 Record ID
jkandiko
Member Posts: 3
I have the following as a record id in our table:
0x70000000027B0636003300390030003100340000000000
I can infer that the first four bytes, in little endian format (00 00 00 70) are 112.
I imagine the next byte, 02, is a signifier to state the key is two bytes: 7b 06 . But this into decimal is 31494. I don't think this is correct. The key in the table is a code20. Does that correspond to 31494?
Or is 02 a signifier for something else? 7b is 123, but I can't figure out what that would correspond to. 06 would explain the following:
36 00 33 00 39 00 30 00 31 00 34 00
When I remove the zeros and convert to a string, I get 639014 .
Is this the correct way to interpret this format for Nav 2015? I believe the MSDN article found
here is specific to 2009 and doesn't equate to 2015.
Can someone tell me if this is accurate? What are those three bytes (02 7b 06) between the table identifier and the record identifier?
0x70000000027B0636003300390030003100340000000000
I can infer that the first four bytes, in little endian format (00 00 00 70) are 112.
I imagine the next byte, 02, is a signifier to state the key is two bytes: 7b 06 . But this into decimal is 31494. I don't think this is correct. The key in the table is a code20. Does that correspond to 31494?
Or is 02 a signifier for something else? 7b is 123, but I can't figure out what that would correspond to. 06 would explain the following:
36 00 33 00 39 00 30 00 31 00 34 00
When I remove the zeros and convert to a string, I get 639014 .
Is this the correct way to interpret this format for Nav 2015? I believe the MSDN article found
here is specific to 2009 and doesn't equate to 2015.
Can someone tell me if this is accurate? What are those three bytes (02 7b 06) between the table identifier and the record identifier?
0