-
To update readonly fields with Javascript simply use setSubmitMode() after setValue() function.
-
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…
-
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…
-
Actions in Dynamics 365 are a type of process that used to extend the functionality of Dynamics 365. You can invoke actions through a workflow, plugin, Javascript or API. We can pass the Input parameters to the custom Action and the results can be set as Output parameters. C# Code of Reading Input Parameters and…
-
To make the form read-only in Dynamics 365 you have 2 options. Either changing record status to Inactive or making all form fields disabled with Javascript. Changing record status to Inactive might not suitable for some business cases. For example you might want to make your form read-only based on an attribute. If you change…
-
In Dynamics 365, you can call an action directly from JavaScript with its inputs. This can be achieved using the WebAPI. First, let’s create a new custom action in Dynamics 365. Our action will accept RecordURL, Prefix, FieldsToIgnore parameters. Then it will create a copy of the Record by querying its metadata. RecordURL – Input string…