Microsoft Dynamics CRM (Archived)

How do I remove default attendee from "required Attendees" in Appointments

(0) Share

Report

Posted on by Anthony A

230

Hi guys,

When we create a case we put a primary Contact.

Then when we create an new appointment in regards to that case, by default the primary contact from the case is put in the field "required Attendees".

How do I disable this? if my user forgets to clear this field an email is sent to the primary contact when he saves the appointment. (I don't want this by default!)

I created a workflow "Start after record is created" and i tried clearing the field but it does not seem to make much of a difference.

I also noticed that if I create an appointment via a workflow and put nothing in that field the appointment gets created without this information...

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

Suggested answer

Mahadeo Matre 17,021 on at

Like (0)

Report

Anthony,

Try putting Javascript on form load of Appointment Entity.

And on load of Appointment, if form is in CreateMode only then clear attendees field.

So that attendee field will not be cleared when appointments which are already created and required attendees.

Hope this will help..

Was this reply helpful? Yes No
Suggested answer

Mamatha Swamy 5,426 on at

Like (0)

Report

Adding to Mahadeo's response, javascript would be the best option to clear the RequiredAttendees field.

In addition to checking that the Form type is Create, check that the regarding field is filled and is of type case. This will ensure that you clear the RequiredAttendee field only on Create form and when the related to case.

Using a real-time workflow to clear the field might lead to same result but will affect the system performance. Also, not sure how the email notification is configured in your CRM. It is best to do these changes at the form level (script)

Was this reply helpful? Yes No
Suggested answer

PS 23,577 on at

Like (0)

Report

Create a workflow on appointments

Run on create

check condition-if regarding case (case) contains data

update appointment>> Required attendees= owner of case

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

As has been said before, just add a few lines of JavaScript to remove the value of the required attendees field on load when a new Appointment is being created.

Unlike before, here's some java script that should do it;

if(Xrm.Page.ui.getFormType() == 1)

{

Xrm.Page.getAttribute(“requiredattendees”).setValue();

}

If a user wants to create an Appointment where the required members are notified of Appointment changes, they can still add contacts to the “Required” field.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

How do I add this script to CRM? I have tried to create a jscript library and create a function for this script. Then assign it to on create event on form, but i get errors.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I have the same problem here. How do I apply this code? What I've tried so far is:

- Create a Library Prevent_Mail with this code:

function preventmail(){

if(Xrm.Page.ui.getFormType() == 1)
{
Xrm.Page.getAttribute(“requiredattendees”).setValue();
}
}

Than I created an OnLoad event calling the Function preventmail but this leads to an error.

How to fix this?

Best,

Hannes

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Sorry to bring this thread back to life a year later, however this is the first result in google when searching for how to complete this task

The above didn't work for me, until I simply changed the quotation marks to "" instead of “”

function preventmail(){

if(Xrm.Page.ui.getFormType() == 1)

{

Xrm.Page.getAttribute("requiredattendees").setValue();

}

}

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hey,

I have to dissapoint you: This nerver worked fine for us, as you can not trust JScripts in Dynamics 365 100%. So we had cases mails going out, even with this active rule. The reason is, the rule didn't run in this cases.

In the end we had to forbid the usage of appointments. This is not a solution, but there's no one you can trust. Poor, but true.

Best,

Hannes

Was this reply helpful? Yes No