Problem with creating General Journal from report.

dannyc
Member Posts: 2
Hi All,
New Member Hope you can help.
Currently using Version4 Navision.
I have created a report which generates a General Journal using the insert command. Most of the data is transferred to the Journal however one variable which is a dimension will not transfer to the Journal. This variable is a code type.
I have confirmed within the report that the variable is holding the data prior to the insert command.
Can anyone help?
Regards Danny
\:D/
New Member Hope you can help.
Currently using Version4 Navision.
I have created a report which generates a General Journal using the insert command. Most of the data is transferred to the Journal however one variable which is a dimension will not transfer to the Journal. This variable is a code type.
I have confirmed within the report that the variable is holding the data prior to the insert command.
Can anyone help?
Regards Danny
\:D/
0
Comments
-
are you doing a VALIDATE somewhere, of anything, after the Dimension has been assigned?
If so it's probably clearing the field.0 -
For example only.
Say I entered some sales lines now I want to do something to update a field in each line.
If I Salesline.VALIDATE."No." I will lose my Quantity field.
Unless store the value somewhere & bring It back.
vStoreQty := Salesline.Quantity; //move it safe
Salesline.VAIDATE."No."; //validate the field I wanted
Salesline.Quantity := vStoreQty; //Move it back0 -
dannyc wrote:Hi All,
New Member Hope you can help.
Currently using Version4 Navision.
I have created a report which generates a General Journal using the insert command. Most of the data is transferred to the Journal however one variable which is a dimension will not transfer to the Journal. This variable is a code type.
I have confirmed within the report that the variable is holding the data prior to the insert command.
Can anyone help?
Regards Danny
\:D/
Because the dimesnions are transfered into linked table, you need to insert first the line, than validate the dimension field on the line and make MODIFY(True). In this way the dimension will be saved correctly. It means you need to keep the steps like this:
1) INIT
2) Assign primary key fields (Template, Batch, Line No)
3) Insert(True)
4) Validate all other fields
5) MODIFY(True)
in this way you fully "simulated" the manual data entering and the result will be correct (if you validate the fields in correct order)0
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions