Oh yeah I was just listing comment fields that would need to be changed if you wanted them all to have nvarchar(max). Never mind…
For real though, nvarchar(max) is 2 GiB. The UI change is annoying. The database fields that are granted 2 GiB of storage per row need correction.
That’s enough to store text instructions, and an instructional video, and a music library to play while doing the operation, and technical drawings of what to do, and the source CAD files, and a CAD viewing software installer, and etc. on every ECO operation row.
3 Likes
This is causing an issue for my customer service team too. I also put in a support ticket, and they gave me the same answer of editing it in application studio. Doing this is a lot easier imo, can someone mark this as a solution?
Not sure why Epicor would change this when it was working just fine but oh well.
Marked the appropriate post as solution. (Although I’m not sure I like this solution very much!)
Klincecum edit: I marked something else, and linked the other as a workaround until they truly decide what they want to do.
1 Like
Hey Folks,
First of all, apologies for the inconvenience.
I’ve re-opened the respective ticket under development, because as mentioned already in this thread, the 1000 character limit should be treated as a MAX. I have also informed the developer that was previously assigned to this to take a look as soon as he is available.
Hope this info is useful, and again, apologies for the inconvenience 
11 Likes
Glad to hear there is a solution.
We are shut down right now due to this change.
@DavidMartinezEpicor Will we see this as a Patch change soon?
Just modify the extended properties?
The fix is to change it to x(9999) or however many characters you need in extended properties. Working fine for us.
1 Like
I had discovered back in E10 that the x(1000) setting actually behaved like an “unlimited” setting in the actual database (a developer and myself actually tested it out in our test environment by copying and pasting an entire word document into the field and then saving it… and it was well in excess of 10,000 characters.
Neither of us were happy with that, because it’s usually only a matter of time before something that isn’t working as a proper control ultimately starts working as designed… at some point in the update/upgrade process. Whether it was Microsoft or Epicor… one way or another, it was going to bite somebody.
1 Like
1 Like