Dynamics crm: role of non event dependencies in form

In our Dynamics CRM In the form , We can use some methods to ensure JavaScript The fields used by the script will not be deleted from the form , You can use Non-Event Dependencies.

For example, we have a function to display the value of a field and print it out , Like this :

function displayWebsite()
{
	alert("The website entered is: " + Xrm.Page.getAttribute("websiteurl").getValue());
}

We add it to the Onload Incident , At this time, when we enter a record, it will show

  At this time, if we remove from the form Website The field will be displayed as

  So if we want to protect this field from being removed from the form , We can use Non-Event Dependencies, Now let's talk about its usage :

1. Form Properties -> choice Non-Event Dependencies This tab page

2. add to Website This field goes to the right Dependent fields in

  At this time, we will see a lock mark next to this field

At this time, if we try to remove this field, the following error will be reported :

  And when we check the properties of this field, we will also find ,'Lock the field on the form' This checkbox It's not editable

We have to put this Website Fields from Non-Event Dependencies Remove the , The above setting will become editable again

But this setting is still selected , That is to say, it is still irrevocable , But at this time, we just need to uncheck it , This field can be removed .