Customer experience | Sales, Customer Insights,...

CRM on-premise v9.1.26.23 Description field of Email can not work well in the Form

(3) Share

Report

Posted on by IvanLiu

Hi All,

As the latest Service Update 1.26 already was available, we patched it last week. But when we did the sanity test, we found the Email form can not work as usual.

The Description field on the form can not now view/update, and displays blank space where it is used.

Did anyone else have the same experience? How can it be fixed.

Best Regards

All responses (8)

Answers (0)

MLarsen 473 on at

Like (0)

Report

CRM on-premise v9.1.26.23 Description field of Email can not work well in the Form

I am also experiencing the same issue. Has anyone told Microsoft about this? Their fixing it or?
Suggested answer

PhilipK 611 on at

Like (0)

Report

CRM on-premise v9.1.26.23 Description field of Email can not work well in the Form

The workaround to this issue is to enable the RTE (Rich text editor) control on the description field.
Navigate to the Email entity via Customizations and edit the forms you are using and add as per the following images

1. Edit the Email form, put your marker on the description field(body) and chose Change properties, and go to the Controls tab and chose add control.

2. Add the Rich Text Editor Control.

3. Enable the control for desired clients, e.g. Web.

Lastly, don't forget to Save changed and publish them.

Best regards.
Philip
Community member 8 on at

Like (0)

Report

CRM on-premise v9.1.26.23 Description field of Email can not work well in the Form

This is still an issue.

In my attempt to find a workaround, at least I want to share my insights here.
By digging through the Debugger, I ended up finding this uncatched error in ActivityEditorControl.js

_this.preview.addSandboxAttributes is not a function

This seems to be the cause, that the editor is collapsing in the browser.

It appears consistent across our clients and, I'm confident, that this is related to the issue.

This affects every entity that uses the default email in UCI. (email, template, emailsignature)
Community member 8 on at

Like (3)

Report

CRM on-premise v9.1.26.23 Description field of Email can not work well in the Form

This is also not working for us since the upgrade.

All email forms description fields (the main body of the email) in not visible in the forms, it is only visible in views, and advanced find, however that's useless when you are trying to write an email.

This needs to be fixed ASAP.
IvanLiu 35 on at

Like (1)

Report

CRM on-premise v9.1.26.23 Description field of Email can not work well in the Form

HiLeah Ju ,

I tried to switch to other type form, all of them can not display the Description field correctly. It looks like the component not works well.
Leah Ju Microsoft Employee on at

Like (1)

Report

CRM on-premise v9.1.26.23 Description field of Email can not work well in the Form

Hi Partner，

Have you tried to switch to other forms to check this field value?

You can also check the properties of the description field to see if anything has changed.
PhilipK 611 on at

Like (2)

Report

CRM on-premise v9.1.26.23 Description field of Email can not work well in the Form

I was to post on this myself on this but yes, you are not alone on this and it came with the latest Update 1.26 (9.1.26.23).
Some would argue a working e-mail is kinda crucial for a CRM system so yeah... Microsoft really need to address this issue asap.

From what I see the the v9.1.26.23 package contained some updates to solutions where one is for the Rich-text-editor(RTE) which I think is the suspect here.

From my testing, the issue with the Email form appears only in the UCI and not it in the old "classic" UI.
So hopefully someone at Microsoft's Dynamics 365 On-prem Team sees this post and provide a fix.

Best regards.
Philip
IvanLiu 35 on at

Like (2)

Report

CRM on-premise v9.1.26.23 Description field of Email can not work well in the Form

After we create one new ORG, change the application to Use Unified Interface only, the issue happen too. Is it a known issue?