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
- 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
Options
Item and Item Description Error on entry
noved
Member Posts: 15
I have stumbled on a peculiar situation in our Navision 3.6 environment that I cannot explain. It relates to the Item Number and Description field that can best be described by example:
Item Number = 1117335
Description = VPL-8503 24X24X12 Filter
Here is the problem: A sales line is entered and the Item No. value VPL-8503 is entered (which does not exist). Rather than the expected error message stating that the item number does not exist, the value 1117335 is populated in the item number field on the sales line when you tab off the field. (':shock:')
I cannot find any rhyme or reason for this happening. The Description field on the Sales Line table is not a flow field or anything unique. Now if the VPL-8503 portion of the Description field in the Item Table is moved to the end of the field (resulting in the description being 24X24X12 Filter VPL-8503), this situation does not occur. That is, if VPL-8503 were entered on a sales line in the No. field, the expected error that the item does not exist is provided. ('](*,)')
This situation described literally happens wherever you would enter the item as described (sales price entries, purchase price entries, PO Lines, etc.)
Has anyone seen this before or have any idea how it would occur or be prevented other than what was described?
Thanks in advance for your response.
Item Number = 1117335
Description = VPL-8503 24X24X12 Filter
Here is the problem: A sales line is entered and the Item No. value VPL-8503 is entered (which does not exist). Rather than the expected error message stating that the item number does not exist, the value 1117335 is populated in the item number field on the sales line when you tab off the field. (':shock:')
I cannot find any rhyme or reason for this happening. The Description field on the Sales Line table is not a flow field or anything unique. Now if the VPL-8503 portion of the Description field in the Item Table is moved to the end of the field (resulting in the description being 24X24X12 Filter VPL-8503), this situation does not occur. That is, if VPL-8503 were entered on a sales line in the No. field, the expected error that the item does not exist is provided. ('](*,)')
This situation described literally happens wherever you would enter the item as described (sales price entries, purchase price entries, PO Lines, etc.)
Has anyone seen this before or have any idea how it would occur or be prevented other than what was described?
Thanks in advance for your response.
0
Comments
Go to the item table->designer->View the properties of the "No." field
you will see a AltSearchField.
Since you item # is very similar to the description it's finding it.
For example if you changed that altsearchfield to look at UPC codes then you could either enter an item # or a UPC code and get the proper item appearing.
you can also F1 on the altsearchfield - to get further details on how it works. Removing the property value will disable it.
You'll see this in many places. try typing the customers name instead of the cust# in the cust no field on the sales order, etc etc.
http://www.BiloBeauty.com
http://www.autismspeaks.org
This is a "feature" of Nav - if the item does not exist then it searches the search description of the item - try entering touring into the No. field in Cronus and you get Item 1001.
This doesn't seem to fire any C/AL code so I don't think you can turn it off. Only thing I can suggest is to blank the search descriptions if you don't want this "feature"
It's handy once you get the hang of it
Dynamics Nav Add-ons
http://www.simplydynamics.ie/Addons.html
Didn't know this one :oops: -thanks for enlightening me
Dynamics Nav Add-ons
http://www.simplydynamics.ie/Addons.html
Then on the OnValidate Trigger of the form, do a Item.GET("No.") on the No. field to ensure they're getting the proper item no.
the problem with this solution is that if you decide to RENAME an item number, sales lines will not be affected.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
Thanks again,
Devon
we use #'s 10000..99999 - make order entry very easy when the person doesn't have to take there hand off the Num Keys.
We used to have Descriptive #'s but after a while they fell apart for us and having to switch between letters & numbers is really time consuming.
So when we went from Macola to Nav it was suggested we change our item numbers at that time (still keeping the old numbers in field No. 2 just in case) But now No.2 is a relic and nobody ever looks at that old # anymore.
It was a good change..for us.
http://www.BiloBeauty.com
http://www.autismspeaks.org