Howdy, Stranger!
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
- 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
- 304 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
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Dimension problem in Vouchers
abhi1901
Member Posts: 102
Dear Expert,
2-3 of our clients are facing problem while entering dimensions in lines in Bank/Cash voucher.
Problem:- They enter dimension while making the voucher and again after some time when they goes to Line --> Dimension then they are not there.
I have confirmed that Every user is entering values in different batch/template.
I have made Delayed Insert property of voucher set to no, because if this is yes then data will move into table when they goes into next line and therefore line no will then only be updated. So do it has any adverse effect.
And also give me some solution to correct dimension problem.
2-3 of our clients are facing problem while entering dimensions in lines in Bank/Cash voucher.
Problem:- They enter dimension while making the voucher and again after some time when they goes to Line --> Dimension then they are not there.
I have confirmed that Every user is entering values in different batch/template.
I have made Delayed Insert property of voucher set to no, because if this is yes then data will move into table when they goes into next line and therefore line no will then only be updated. So do it has any adverse effect.
And also give me some solution to correct dimension problem.
0
Comments
In standard journals, changing the DelayedInsert property won't cause dimension problem. You can debug the corresponding field's validation and also Insert trigger to find the reason.
Pargesoft
The objects are not modified.
Also we are using debugger and using break point on every trigger of form, table and codeunit from last 20 days but finding no solution or the point of problem.
So have made new table for entry dimension and then flow it from my table to all tables.