I would like to expand the vendor name and Customer name field from size 30 to 50. Is there any objects or methods that can help me to do this? If not, i have to go through the table and object manually to change it which is quite time consuming and also i might miss out the table or object that use these 2 fields. I would appreciate if someone help me on this. Thanks
I suggest that you use the Customer Name 2 and Vendor Name 2 fields. Then split the input (50 characters) over Name and Name 2. The Name 2 fields are already present, and everywhere where the Customer/Ventor Name/Adresses are printed they are included in the address. This way you don’t need any modifications to the data structure Lars Strøm Valsted ------------------------- Why can’t programmers tell the difference between Christmas and Halloween? Because OCT(31) = DEC(25)
HI Lars, Thanks for your fast response. If i would to use Name 2 field, i still have to find out what are form using the name and name 2 field, then do the splitting of the data before saving, right? I would prefer don’t have to go through object by object, due to i am not sure what are the objects using the field.
Hi! For automatically splitting the Input-string, I would recommend to create a new field (e.g. “Input Name”, Type Text, Length 60) in the customer table, and then do the split in
Input Name - OnValidate() VALIDATE(Name, COPYSTR("Input Name", 1, 30)); "Name 2" := COPYSTR("Input Name", 30);
After this, you only need to show the fields “Input Name” and “Name 2” where needed. Regards, Jörg Joerg A. Stryk Apollo-Optik, IT/ERP
You should never change properties of standard-fields! This could cause a lot of trouble and errors in the whole system. E.g. if you change the field-legth of “Name” in the “Customer” Table, you have to change in Table 36 “Sales Header” (?): “Sell to Name” “Bill to Name” “Ship to Name” … the same in table 110, 112, 114 and many others, otherwise an error will occur when creating/posting a sales order. Also an update of you NAVISION-Version would be more difficult, time consuming and … expensiver! Joerg A. Stryk Apollo-Optik, IT/ERP
Well I don’t know about never, what is life with out a bit of fun. It would take no more that a day to do, but don’t forget it is not just the field lengths in tables but also the length of text variables as well. If you can then I would use name/descripton 2 as this would only be a case of designing them on the relevent forms. Paul Baxter
I’ve always found the biggest hassle of extending field lengths has been the redesign of reports that is required. When printing the now longer fields on reports, in many cases, those will then overlap some other column of data. That column will have to be shifted, then the next, then the next, and so on. For fields that are widely used, like Item Description, the affect on reports is the nightmare of extending the field length. Dave Studebaker firstname.lastname@example.org Liberty Grove Software A Navision Services Partner
Just to answer one of the original questions: As I understand it, there is a tool that can assist you in finding the fields on the forms, reports, tables etc… You can use the “Where Used” option in the Navision Developer toolkit and this “should” point out all the instances of the two fields you are talking about. I have not used this myself, so I could not swear to this, but this is its use as I have been told.
Dean, yes, “where used” is exactly the function a developer could/would use. But the original question was asked by a ‘Beginner End User’. I guess this user - has no ability to uses the developer toolkit - has no license permission to export objects to text files Perhaps Rachel can tell us the Navision version and someboby can generate a reference file using the developer toolkit. Regards Walter
Hi guys, Thanks for your response. I appreciate it very much. I know that changing the field properties is going to be torblesome. But i have no choice, have to expand the field size. Seem like i have no many options, but to do it manually. I will try the “where used” option in Developer toolkit. Walter, thanks for your suggestion on creating the reference file for me. Anyway, i will try to get the reference myself. Will ask for help if i cann’t get it.
Hi, I’ve done this change for a customer and it is not nice. If it is the only solution open to you then be aware of the following: 1) Reports will need redesigning 2) Any variables that reference the name fields will need to be checked. 3) Any transfer field commands will need to be checked and a decision made on how to handle the transfer. My advice is to find an alternative solution
The alternative would be to upgrade to attain which has a customer name field length of 50! Paul Baxter
If Attain/Financials had “Extended Datatypes” as Axapta, this problem would not be a problem at all.
Hi, it seems that expanding data fields length is the only solution for a lot of companies. I’ve done this choice, but, after 1 year, some times an error window still pops up telling about the wrong length of a variable. Yeah, it’s a mess!!!
Never ever is the field length extension handy or easy. But in newer Navision territories e.g. India, longer names are a common occurence and it becomes hell of a task explaining to the client the labour involved to accomodate this simple demand where all the local standard solutions very competently do this. 1. Of course expanding solution by NTR in localisation is one solution but this also means delay in getting local versions for every Attain release which hopefully shall be more frequent in future. 2. There is no limit of this expansion. Size 60 is one client’s request. Another one could ask for more. But at the end of the day effort required never justifies the requirement. Project Manager Euroinfo Systems