We have noticed that the comments on a job operation seem to be limited to 1000 characters. We will need to expand this limit to much more than the 1000 limit. More like 30,000 in some operations. We see have found that this character limit can be increased via the Extended Properties and navigating to the comments on the ECOOpr table. Are there any repercussions to expanding the allowed character limit to whatever we need? When we upgrade the software moving forward will these changes revert back to standard or be kept as is? Any info anyone can provide would be much appreciated, I don’t want to assume making this change won’t cause any issues moving forward. Thanks, Mark
Generally, 1000 has been the same as MAX. Have you tested the limit? or are you just seeing that in the properties?
I do think I remember seeing somewhere that the browser UI was honoring that 1000 as actually 1000, but I haven’t messed with it myself. It would be interesting if you try it in both places and see if they act different.
As far as changing the properties, if the extended properties are less than what’s in the database, you can set it up the size in the database. But if the database field is less, you can’t go over. In this case, the job comments field is a MAX field, so you should be fine.
Yeah, it started on 2024.2.
2 Likes
In a previous company I worked with, we used many characters in this field. Per an update from an Epicor Employee on the thread Mark_Wonsil linked above, x(1000) should be treated as nvarchar(max).
Should be, but that doesn’t mean it’s fixed yet lol.
1 Like