HDCase.IssueDescription x(1000)?

Hey everyone. I have a user complaining about not being able to change the case description. I have found that on a field that is supposedly formatted to fit only 1,000 characters we already have about 1200 characters being stored. How could this happen? Users aren’t able to add text to the field but they can remove the text, because it has already exceeded it’s limit. Yet, the database stores all 1200 characters no problem. Anyone have experience with or background information on this field?

Thanks.

The DB should handle it no problem… but the UI is probably limiting it. Not sure how you got the extra characters in there, though.

DMT could’ve circumvented the UI logic. Or maybe it’s new UI logic? Wasn’t there just an update over the weekend for SaaS customers.

See the other thread about ecoopr. Same problem same solution.

2 Likes

There was just an update. And we’re assuming this is what happened. In application studio though, the Max Limit is actually blank, so I’d assume it’d default to the databases format. Just a little confused how the database is that loose with defined character limitations. Other fields throughout Epicor I do not run into the same behavior.

@jott
See other thread on workaround using extended properties

Thank you. Reading through it now.

Good thing they fixed the glitch. The rest should work itself out naturally.

2 Likes

It’s not a glitch, they just fixed something that wasn’t broken.

X(1000) has never meant 1000 characters in Epicor land, it’s always been shorthand for Max.

It looks like they are going to unfix it.

1 Like

My opinion … all two-cents-worth.

X(1000) being equal to X(more than two billion) is not good and is certainly not self-evident. If we need a KB article to tell us that X(1000) is X(MAX) … then something is broken.

The only thing wrong with this update is that it is a breaking update that was not communicated beforehand. Otherwise, it’s a thing that ought to be done at some point :man_shrugging:

3 Likes