I have a client who would sign up today for D365 Financials if the Item Description field was larger. right now it appears to be limited to 50 characters. He need it to be at least 1000 characters.
I am aware of the extended text availabliity, but these also are limited to 50 characters and to enter the description they need 50 characters at a time is a poor work around.
I strongly agree with the larger item description field. This is very critical to our business to have a larger description field. This is just as critical to the line item description on a purchase order.
2 years ago it was suggested, what is the status at the moment?
Developers can't force the president of the company to engineer their data 'properly'. What we usually here is "We want to do this for now, and we can revisit making it 'right' sometime in the future." Speaking from experience.
Even if a company is forced to segregate their data into attributes or other fields, those fields will need to be added to every downstream artifact in the same place the longer description field would have been. And if they don't have an internal developer then they have to pay to have their vendor add the fields/attributes everywhere etc.
I fight for 'the right way' a lot where I'm at and about 50% of the time I get shot down due to various reasons. "This is the way our old system worked so we need to keep it this way for now. We don't have the resources to modify all our reports and queries, etc."
Would you really turn away a new customer rather than accept a 100 character description field?
In my opinion changing the text size would have a large impact with internal views and lists, but the largest impact is in comuication with other systems, they often have a structure like Description, Description2, DescriptionX,,Long Text.
The next with long texts is, do you want to show your large description on every picklist, workpaper, or iventory counting list? I think no.
I think the best would be, having Extended Texts which are realy extended texts with more than 50 characters like a BLOB an editable text field with more than three lines and the possibility to configure on which document this text is printed.
I agree. The more characters that can be added the better.
Extending the description makes no sense to me, since whatever length MS will come up with, it will be too short.
Understand Item Description as internal information for searching and filtering in list pages. For longer description, use the extended texts (they have infinite characters, since you can have infinite rows per item) and customize your reports or just let the “internal” description sit there - that is common with most documents I came across.
Changing the length of the description field has a wide imdact, since it is populated to all documents, to ledger, archive, reports, etc. When starting with items, we also want to extend the description at resources, GL, Vendor, Customer, etc since they follow the same rule.
This will end up in huge database sizes for long, but (almost) empty fields.
We have run into this issue as well. 50 characters is much too short, and using the ext description or description 2 is awkward. There is a note that this is Planned. Any details on when it is planned for and how many characters there will be?
1. Item no. should be longer at least 40 characters.
2. Item Name suggest 100 chars.
I am against to extend the field. If it is description, it should be in different field than Name. If the name need more than 50 chars, I expect that it includes data, which are not supposed to be there. E.g. we have one Wine importer and they wanted to put the name, year, supplier and volume (unit of measure) into the name. Yes, this is long. Right now we are changing this and they will put the name and year there, but supplier and volume will be in different fields. Best is to put them into attributes and than it is question how to show the attributes when looking up the item...
Which problem are we trying to solve: 1."Description is too short to enter product name" or 2."Description is too short to enter detailed description of product"
If the answer is "2", how this extended description to be used? Should it be printed in documents/reports? Should it be visible in the list page? Is it needed in the journals, document lines, BOMs,...?
Business Central Team (administrator) on 5/17/2022 1:18:24 PM
Thank you for your feedback. We released this feature as part of the functionality in Business Central April 2019 release. Please refer to the following link for more information: https://docs.microsoft.com/en-us/business-applications-release-notes/April19/dynamics365-business-central/application-enhancements Sincerely, Business Central Team