Hi Marcus,we had the exact same issue when we setup email to case rules.
What we did is the following:1) Create the case with a placeholder text like: "this description will be overwritten with the email content"2) create a Microsoft Flow (ahem, Power Automate I should say...) that runs on Case Create to parse the HTML content of the email to a string using the "HTML to String" component3) we have a field length of 500 char setup, so I built in a condition to say: If length of email is less than 500 char, transfer full string to description field, else: truncate string to 500 char (using sub-string) and then place it in the description field (assuming that the first 500 char of an email is enough to understand the context of the case.attached a screenshot of what we did.
This prevents case creation to fail on a too long email, and will make sure that the description field is not too long (20,000 char is way to much if you ask me).
The Flow will run almost instantly, so almost as soon as the user opens the created case, the email body will be there already.
Hope this helps!
You can always shorten the field length if you desire. Emails that are too long will be cut off automatically. If you're concerned of losing valuable information on older records, you can do something like exporting all cases you have now to Excel and check the length with '=len(A1)', filter for any descriptions that are longer than your newly selected field length and manually decide what to do with those that go over that length.Most emails we see at clients are short and to the point. When someone feels the need to write a book in an email, no-one will take the time to read it anyway ;-)Good luck with whatever way you decide to go!
If you've found this thread useful, dive deeper into User Group community content by role