In CRM it is common that showing different forms to different user gropus. There might be some conditions that you check to switch and show different forms to users. For cases like these, formSelector() and navigate() functions save the day. formselector.items collection: A list of all the forms accessible to the current user. Only those forms … Continue reading Dynamics 365 – Switch Forms Dynamically by Using JavaScript | formselector
Tag: Dynamics 365
Dynamics 365 – How to Show/Hide Sections and Form tabs
Just like attributes, tabs and sections are also controllers of the forms in Dynamics 365. You can apply same logic to show and hide those controls by using Javascript. For the tabs; you need to know unique name of the tab you are going to show/hide.For the sections, you need to know unique name and … Continue reading Dynamics 365 – How to Show/Hide Sections and Form tabs
Dynamics 365 – Share-Unshare Records with Plugin or Custom Workflow Activity by using C#
In Dynamics 365, you can dynamically change access privileges of users or teams to records by using Plugins or Workflows. There could multiple scenarios you can implement such functions. For instance, when creating a new Record you can share that record with a specific team or user by using GrantAccessRequest message. Again, on changing of … Continue reading Dynamics 365 – Share-Unshare Records with Plugin or Custom Workflow Activity by using C#
Dynamics 365 – Different Ways of Showing Form Level Error Messages – setFormNotification | setIsValid
Form notifications are useful when you want to prevent the user saving the form if the form fields do not meet the conditions. Say you have 2 date fields called "Start Date" and "End Date". You want the records can only be saved if the "End Date" is bigger than the "Start Date". You have … Continue reading Dynamics 365 – Different Ways of Showing Form Level Error Messages – setFormNotification | setIsValid
Dynamics 365 – How to get and use formContext
The formContext is a part of executionContext and it replaces deprecated Xrm.Page starting from Version 9. Xrm.Page object was used to represent a form or an item on the form. With the latest version, the Xrm.Page object is deprecated, and you should use the getFormContext method of the passed in execution context object to return reference to the appropriate form or … Continue reading Dynamics 365 – How to get and use formContext
Dynamics 365 – How to Trigger OnChange Event of an Attribute
fireOnChange() function is used to trigger the registered onChange events of an attribute. It is also very useful when you update an attribute through Javascript Code and it onChange event doesn't trigger. When you update an attribute from Javascript code, its onChange event doesn't trigger. If you want it to be triggered, you have to … Continue reading Dynamics 365 – How to Trigger OnChange Event of an Attribute
Dynamics 365 – How to Customize Opportunity Close Form
Before you customize the Opportunity Close form, you need to enable the customization of Opportunity Close form from System Settings. To do that open your Advanced Settings page. Go System > Administration > System Settings. Under Sales tab enable the Customize close opportunity form. Once you enable it, users will start seeing the Quick Create … Continue reading Dynamics 365 – How to Customize Opportunity Close Form
Dynamics 365 Updating Readonly Field – setSubmitMode()
To update readonly fields with Javascript simply use setSubmitMode() after setValue() function. always: The data is always sent with a save. never: The data is never sent with a save. When this value is used, the column(s) in the form for this column cannot be edited. dirty: Default behavior. The data is sent with the … Continue reading Dynamics 365 Updating Readonly Field – setSubmitMode()
Property ‘field’ on type ‘Microsoft.Dynamics.CRM.entity’ is not a navigation property or complex property. Only navigation properties can be expanded
This is a common error message when you are trying to use multi-type lookup fields(i.e regardingobjectid, customerid, activityid) in odata requests to expand(join) entities. It basically says the lookup field you are expanding to does not have a navigation property for that entity. You just need to tell the web api which entity you are … Continue reading Property ‘field’ on type ‘Microsoft.Dynamics.CRM.entity’ is not a navigation property or complex property. Only navigation properties can be expanded
Dynamics 365 Web Api – How to Set Lookup Field Value
When updating lookup values, or using lookups in entities you must use the @odata.bind annotation to set the value. The syntax for this is: {field_name@odata.bind: "/entitypluralname(guid)"} Some examples: ownerid@odata.bind:"/systemusers(a30cbf7b-69cd-4299-b468-b4978f716af7)"opportunityid@odata.bind: "/opportunities(a30cbf7b-69cd-4299-b468-b4978f716af7)" For lookups that have different possible entity types(i.e regardingobjectid), this changes slightly (note the entity logical name at the end of the "name") parentcustomerid_account@odata.bind = … Continue reading Dynamics 365 Web Api – How to Set Lookup Field Value
Crm Minds 