Item Code Length change from 20 to 30 Problem

apsingh

Hi,
I want to change Item Code length from 20 to 30. I have used Toolkit where used option but the result are not satisfactory.
If you have any code or solution for this pls let me know.


Regards,
Anup Pratap Singh

ssingla

Dear Anup,

You might have to modify a lot of properties/code/variables which is not advisable. The other solution can be adding a seprate field in the item table 0f 30 length. The same can be used anywhere in the reporting or else where wherever required.

ara3n

You can use the search Description field. The plus side to this field is that on sales order you can type search description and Navision will find the item.

Alex_Chow

I hope you guys fought to the teeth with the client against this change. It will cost them a lot of money to upgrade and apply hot fixes in the future.

David_Singleton

deadlizard wrote:

I hope you guys fought to the teeth with the client against this change. It will cost them a lot of money to upgrade and apply hot fixes in the future.

I think that every developer I know has done this mod EXACTLY once. It takes only one time to learn never to do it again, but it generally takes once to learn.

Alex_Chow

David Singleton wrote:

I think that every developer I know has done this mod EXACTLY once. It takes only one time to learn never to do it again, but it generally takes once to learn.

So true... So true...

ara3n

Ok I'm the first here to say that I have not done this. Although I've upgrade a db that had this mod. In axapta this would be a 20 min mod. So I hope the future Dynamics keeps that feature. It would be nice to have inherited data types.

Marcel_G.

David,

I'll agree with your thought :'I think that every developer I know has done this mod EXACTLY once. It takes only one time to learn never to do it again'
But (oeps...): In the Netherlands there are several options/questions about this...
And the first one is: The customer is KING (??).
The second 'thing': Why permanently more questions and needed solutions about this? Customers 'need' more ?

No hard feelings against you (AND other...)
Just Cust.Feelings := 'ok' + 20'

TonyH

its even better when your customer has a dev license and stumble across their Customer/Vendor No. field length change (Object modified count = 5) and.......... its alright in live.

Had to tell him till I was blue in the face that it would error at some stage. Would believe me so I had to create a test script to prove it.

TonyH

So I guess anup, what everyones saying is, if you can roll it back and tell you customer its not worth the effort in the long run to change the field length, then thats the best solution. Search Desc new field etc...... but no field extensions.

2tje

Tony, search the forum for this subject and you will get a lot of posts about it. Don't change the length of a field in NAV, use another field or create a new one.

David_Singleton

Marcel G. wrote:

David,

I'll agree with your thought :'I think that every developer I know has done this mod EXACTLY once. It takes only one time to learn never to do it again'
But (oeps...): In the Netherlands there are several options/questions about this...
And the first one is: The customer is KING (??).
The second 'thing': Why permanently more questions and needed solutions about this? Customers 'need' more ?

No hard feelings against you (AND other...)
Just Cust.Feelings := 'ok' + 20'

Yes Marcel for sure the customer is King, and that's why we want to deliver the best solution to the King, not just some quick fix that is cheap now, but then ends out costing them more money in the future.

The code field in Navision is not designed for complex searching and structuring of Item or Customer numbers, its really supposd just to be a sequential number. Most clients have a different need in how they search and enter part numbers or customer numbers, and the best solution is to always sit with the client, understand their business needs,a nd design a system based around that need.

Yes there are cases for extending Description fields, (rare but they can exist) the case for extending a primary key is even less common, and would most likely be only in a very highly developed vertical solution (not and never for an Add-On), where many sales of an identical product justify the additional long term support cost.

I canassure you that today somewhere in the world today some sales person is telling a potential client that ther is no problem extending field lengths, and in antoehr part of the world, there is a consultant saying the opposite.

TonyH

2tje wrote:

Tony, search the forum for this subject and you will get a lot of posts about it. Don't change the length of a field in NAV, use another field or create a new one.

Lol, I think you miss read what I wrote

I said a customer had gone and done it themselves!

I think my first unscuessful attempt a field length change was around 1999
Never again! #-o