Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K 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
- 298 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
a bug with Capacity Cost Posting to G/L on SQL Server
mrQQ
Member Posts: 239
Hello,
i just thought i'd mention this bug I found. Hopefully this helps someone.
Basicly, when on SQL server, numeric code fields are sorted differently when on Native client. For example:
Native:
100
101
1000
1001
1100
SQL:
100
1000
1001
101
1100
This wouldn't be much of a problem. However, a temporary table is sorted the "native way", even under SQL client. And here in lies the problem:
R1002, Post Inventory Cost to G/L job, uses temporary table TempCapValueEntry to loop through capacity cost to post, while using actual Cap. Ledger Entry table as data item (presumably to keep grouping). However, these two tables get sorted differently, if Prod. Order Nos. are numeric. And thus, the iteration sometimes finishes without going through all the records needed, and only some of cost gets posted.
i just thought i'd mention this bug I found. Hopefully this helps someone.
Basicly, when on SQL server, numeric code fields are sorted differently when on Native client. For example:
Native:
100
101
1000
1001
1100
SQL:
100
1000
1001
101
1100
This wouldn't be much of a problem. However, a temporary table is sorted the "native way", even under SQL client. And here in lies the problem:
R1002, Post Inventory Cost to G/L job, uses temporary table TempCapValueEntry to loop through capacity cost to post, while using actual Cap. Ledger Entry table as data item (presumably to keep grouping). However, these two tables get sorted differently, if Prod. Order Nos. are numeric. And thus, the iteration sometimes finishes without going through all the records needed, and only some of cost gets posted.
0