Possible bug in NAV2016 - Table 9001 "User Group Member"
rsaritzky
Member Posts: 469
Hi all,
We're on NAV2016 CU5 and ran into a problem on the "Users" list page (Page 9800) and the User Card (Page 9807).
We have a User Group with the "Name" field longer than 30 characters.
Table 9801"User Group Member" has field 6 "User Group Name" defined as a flowfield - the CalcFormula is:
However, the Lookup field in the "User Group" table (Table 9800) for field "Name" is text(50). So if "Name" is longer than 30 characters, you get an error when trying to open up the "Users" page or "User Card" page:
"The length of the string is 31, but it must be less than or equal to 30 characters. Value: XXXXXXXXXX XXXXXXXXXX XXXXXXXXXXX
Page User Group Memberships must close.""
I haven't seen a correction related to this in CU6-CU10 but it seems logical that the flowfield should be the same length as the source field.
I'm wondering if this issue has been reported "officially" to Microsoft, or if it happens to be fixed in CU6-10? We're in the process of upgrading so we are waiting for a later CU before we do a re-merge into our codebase.
Thanks
Ron
We're on NAV2016 CU5 and ran into a problem on the "Users" list page (Page 9800) and the User Card (Page 9807).
We have a User Group with the "Name" field longer than 30 characters.
Table 9801"User Group Member" has field 6 "User Group Name" defined as a flowfield - the CalcFormula is:
Lookup("User Group".Name WHERE (Code=FIELD(User Group Code)))
The field length for "User Group Member" is defined as Text(30).However, the Lookup field in the "User Group" table (Table 9800) for field "Name" is text(50). So if "Name" is longer than 30 characters, you get an error when trying to open up the "Users" page or "User Card" page:
"The length of the string is 31, but it must be less than or equal to 30 characters. Value: XXXXXXXXXX XXXXXXXXXX XXXXXXXXXXX
Page User Group Memberships must close.""
I haven't seen a correction related to this in CU6-CU10 but it seems logical that the flowfield should be the same length as the source field.
I'm wondering if this issue has been reported "officially" to Microsoft, or if it happens to be fixed in CU6-10? We're in the process of upgrading so we are waiting for a later CU before we do a re-merge into our codebase.
Thanks
Ron
Ron
0
Best Answer
-
Please disregard - found the fix in CU10...Ron5
Answers
-
Please disregard - found the fix in CU10...Ron5
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K 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
- 610 NAV Courses, Exams & Certification
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 251 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions