Does someone have a complete description of fields, variables, etc. that has to be changed when the fieldlength of Item Description has to be enlarged (e.g. 30--> 50).
You really do not want to change the field length of any standard Navision master table. It's not difficult to find out where the fields themselves are directly used, but that does not even start to prevent your problems where the field will be used to fill in other fields, or even variables that will be used elsewhere.
We've tried it and had more trouble than it was worth. If you need room for bigger description, just add a new big text field to use for the description and take the original description field off the form. This way you can exactly control where it is used and oyu don't get any conflicts.
I used to work for a UK NSC that produced anmd sold its own variation on standard Navision, which included item description fields and Customer/Vendor/Prospect/Contact Address fields being 50 Char.
Despite making use of suitable tools, every so often an overflow would "come out of the woodwork" and we would have to fix it. Therefore I would not recomend it.
It would be a better idea to make use of the "Description 2" field in the Item table as well as the "Description" field.
We had the same question in a recent project. Instead of enlarging the description field, we added a field with a second description. this way you don't tuch the standard Navision code. In reporting, you can add the two description fields to one description.
We batted this one around as well. We are using the Description 2 line, and sometimes THAT's not enough, BUT extending the original field was NOT recomended due to all the reasons that were stated above.
I would make much more stable to sense from a stability to use the Description 2 field, or even ADD another one, instead of modifying the original code.
I have a package to expand the length to 50 for Item description/description2, Customer Name/Name2, Customer Address/Address2,Vendor Name/Name2, Vendor Address/Address2.
if you want, contact with me, michael.hu@tectura.com
It's for W1 4.0 SP1 and SP2.
and by the way, I modify the length of field though C/AL and modify the length of Variable manually, is it possible to modify the length of Variable through C/AL?
Comments
We've tried it and had more trouble than it was worth. If you need room for bigger description, just add a new big text field to use for the description and take the original description field off the form. This way you can exactly control where it is used and oyu don't get any conflicts.
HTH
RIS Plus, LLC
I used to work for a UK NSC that produced anmd sold its own variation on standard Navision, which included item description fields and Customer/Vendor/Prospect/Contact Address fields being 50 Char.
Despite making use of suitable tools, every so often an overflow would "come out of the woodwork" and we would have to fix it. Therefore I would not recomend it.
It would be a better idea to make use of the "Description 2" field in the Item table as well as the "Description" field.
Lead Consultant
Theta
My opinion is also that you should use another field (description 2 or a new one) as suggested above.
I would make much more stable to sense from a stability to use the Description 2 field, or even ADD another one, instead of modifying the original code.
if you want, contact with me, michael.hu@tectura.com
It's for W1 4.0 SP1 and SP2.
and by the way, I modify the length of field though C/AL and modify the length of Variable manually, is it possible to modify the length of Variable through C/AL?
Navision Consultant
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n