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
- 301 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
Attempt to post Jnl Line clears ShortCutDim3 and then complains about missing Dim3
pdj
Member Posts: 643
(NAV2016 - Platform CU8 build 45046, Application CU5 build 45243)
I have a client who recently started using the third dimension, after having used two dimensions for years.
They have some G/L Accounts set with Code Mandatory for the third dimension and also set up with a default third dimension. In most situations, this works as expected. NAV suggest the specified dimension, but they can change it. If they delete it, it will not allow posting.
However, several users complain that once in a while their Journal behaves strangely. Even when the third dimension is filled, they get an error in Posting saying they will need to enter a third dimension value. When they click Ok then the third dimension value is cleared on all journal lines. They can then enter the third dimension value for all lines again, and during posting, they get the same error. Restarting the NAV client solves the problem, but what is going on?? At first, I didn't believe it, but I got a video recording of it.
I suspected a platform issue, but I can't find anything like this in the CU descriptions.
I then suspected a SingleInstance codeunit in some sort of "bad state" with some filters. I have looked at the list of SingleInstance codeunits in the base, and my only suspect is no. 19: "Gen. Jnl.-Post Preview". I have not dug deep into this one, but we haven't modified it, and we haven't modified anything related to Dimensions either.
My final idea was a usage of FILTERGROUP(1) on a dimension table. I have also searched for that, but also without luck. (The Danish Add-On Lessor uses that a lot, but not on anything related to Dimensions)
Any idea, or has anyone seen this before?
I have a client who recently started using the third dimension, after having used two dimensions for years.
They have some G/L Accounts set with Code Mandatory for the third dimension and also set up with a default third dimension. In most situations, this works as expected. NAV suggest the specified dimension, but they can change it. If they delete it, it will not allow posting.
However, several users complain that once in a while their Journal behaves strangely. Even when the third dimension is filled, they get an error in Posting saying they will need to enter a third dimension value. When they click Ok then the third dimension value is cleared on all journal lines. They can then enter the third dimension value for all lines again, and during posting, they get the same error. Restarting the NAV client solves the problem, but what is going on?? At first, I didn't believe it, but I got a video recording of it.
I suspected a platform issue, but I can't find anything like this in the CU descriptions.
I then suspected a SingleInstance codeunit in some sort of "bad state" with some filters. I have looked at the list of SingleInstance codeunits in the base, and my only suspect is no. 19: "Gen. Jnl.-Post Preview". I have not dug deep into this one, but we haven't modified it, and we haven't modified anything related to Dimensions either.
My final idea was a usage of FILTERGROUP(1) on a dimension table. I have also searched for that, but also without luck. (The Danish Add-On Lessor uses that a lot, but not on anything related to Dimensions)
Any idea, or has anyone seen this before?
Regards
Peter
Peter
0