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
- 269 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 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
Default Dimensions error
beetlestone
Member Posts: 46
Hi everyone.
I have a customer who is using NAV2013 R2 GB 7.10.38053.
One user at this customer is unable to add one specific Dimension value to any record - Default Dimensions, Document Dimensions etc. The error message is
"The field Dimension Value Code of table default Dimension contains a value (AGG001) that cannot be found in the related table (Dimension Value)"
The data they are trying to add is for a PRACTICE dimension and the value is CL.
The content of the error message (AGG001) is wrong, in that the user is not trying to use this value, nor change from this value. The AGG001 value actually relates to a CUSTOMER dimension.
This user can add any other Dimension Value to any record, other than PRACTICE : CL.
Every other user can add PRACTICE : CL to any record.
We have tried to delete the PersonalizationStore.xml, we cannot delete the Dim Value through the GUI because it has already been used in posted docs, tried different hardware for the user.
What does make a difference is if we change the TableRelation property of the Dimension Value Code field on Default Dimension. If the property value is deleted, then the user could manually enter the value without validation. Put the property value back and the error returns.
We have re-compiled objects, logged out in, but now need to have some other suggestions.
Anyone able to help?
cheers,
Darren
I have a customer who is using NAV2013 R2 GB 7.10.38053.
One user at this customer is unable to add one specific Dimension value to any record - Default Dimensions, Document Dimensions etc. The error message is
"The field Dimension Value Code of table default Dimension contains a value (AGG001) that cannot be found in the related table (Dimension Value)"
The data they are trying to add is for a PRACTICE dimension and the value is CL.
The content of the error message (AGG001) is wrong, in that the user is not trying to use this value, nor change from this value. The AGG001 value actually relates to a CUSTOMER dimension.
This user can add any other Dimension Value to any record, other than PRACTICE : CL.
Every other user can add PRACTICE : CL to any record.
We have tried to delete the PersonalizationStore.xml, we cannot delete the Dim Value through the GUI because it has already been used in posted docs, tried different hardware for the user.
What does make a difference is if we change the TableRelation property of the Dimension Value Code field on Default Dimension. If the property value is deleted, then the user could manually enter the value without validation. Put the property value back and the error returns.
We have re-compiled objects, logged out in, but now need to have some other suggestions.
Anyone able to help?
cheers,
Darren
Darren Beetlestone
0
Comments
http://www.epimatic.com
no security filters have been set. We have run the Permission table and all appears to be in order.
It should be noted that the database does have a CRONUS company, and when creating the DIMENSION and Value in CRONUS, the user is able to assign the value to records as required.
All of the other companies are copies of the LIVE company, taken at different times over the last few months. The problem exists in all of the user companies.
Darren
http://www.epimatic.com
The quoted Dim value is actually the first one in Dimension Value table, even if it is for a different Dimension Code.
It is just really odd that this affects only one users ability to apply one dimension value to every record. Everyone else, every other dimension value and every other dimension work without a problem.
In a company without transactions, the problem occurs. Deleting the Dim value, and then recreating it does not change the behaviour, either.