Our Shelf No. (Item table) field is a code field with length 10.
Are their dire ramifications of expanding this field to length 15 or 20?
Obviously, we will also need to update some reports and forms, but that is cosmetic. Is there standard Navision code that will break because we expanded the length of this field?
I ask because I learned here not to expand the length of Description 1 (Item table) unless we wanted to make a ton of programming changes. I searched for this question, but could not find an existing answer.
Thanks in advance!
kind of fell into this...
0
Comments
But 1 thing you can do is: export all as text, import it in the developers toolkit and search where the field is used (remember to search also where the resulting fields are used:e.g. in Codeunit x it is transferred to a field in another table, so you also have to search on that field).
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
I am not a developer, so I cannot do as you described. I will ask our reseller, again, for their thoughts.
Anybody else have any ideas? I believe our Shelf No. field is stock.
RIS Plus, LLC
RIS Plus, LLC
I agree about creating a new field. I'll pass your advice on.
We would still have to make a lot of changes for reports and forms to function as needed.
Now that would be alot easier.
Perhaps they don't have to be as complicated as you have them.
10 digits
0000000001..9999999999
that's a lot of codes and I ddin't even use Letters which will bump you up to trillions of options.
http://www.BiloBeauty.com
http://www.autismspeaks.org
Thanks for all of your advice, everyone.
then I changed the employee table. so that job title field linked to my new job title table. so when we do data entry, the look up selects the title and it is input based on the table. Nothing is ever entered directly, and thus all titles are consistent. Users also like it better because they just select a lookup value from a list.
Now for your situation you could set up a new table called “shelf “, it would have the code and description, the code being a 10 digit field. And the description field as long as you want. Then link this new table with the item table field “Shelf” this way your users could lookup by description and the smaller code would be input in the item card.
This way no code units would have to be changed, and you would only have to modify a few reports to get the description. I do not have the developer license and all this can be done with just the standard report/form/and table designer granules.
So, you would create one table, one lookup form, and modify the item table to use these to populate the shelf field. All Navision functions would be untouched and you might not even have to modify the forms, you could just print out the shelf table with descriptions for a cross reference. Otherwise you could modify the reports to include the description from your shelf table. Hope this make since.
In Navision 2.0 we used bins (the were included in our advance distribution granuls) After upgrading to 4.0, bins required another licensed granule that was pretty expensive.
so, instead we set up a new dimension called bin and set up our bin codes as a dimension instead. You may be able to do the same thing.
RIS Plus, LLC