Calculated Fields in CRM 2015

  • Calculated fields are always performed in real time

  • Calculated fields are always read only

  • Calculated field values are not stored in the MS CRM DB. Instead, a MS SQL function is called in order to perform the calculation and then present the result in a form, view or chart

  • Calculated fields can use data from the same entity or any other related entity. They can only span a maximum of 2 entities

  • Calculated fields cannot be used to trigger events such a workflow or plugins

  • Calculated fields can be used within another calculated field, however you can only have a maximum of 5 chained fields to help mitigate against any potential performance issues

  • If the calculate field results is over 4000 characters, the data will be truncated with no indication made to the user.

  • Calculated fields will not work in offline mode

  • Circular references are prohibited so therefore you cannot reference the same calculated field within the calculation (i.e. within the action section of the calculated field properties)

  • Saved queries, charts and visualizations can only have a maximum of 10 calculated fields

  • You can only sort a view if the calculate field uses fields from within the same entity. If the calculated field used fields from a parental entity, you will be unable to sort on the calculated field.

Comments

Post a Comment

Popular posts from this blog

Workflow Activity Input and Output Parameters and Data Types in MS CRM 2013/15/16

Microsoft Dynamics CRM supports two types of parameters for a workflow activity. Input Parameters Output Parameters Input Parameters The input parameter is annotated with the .NET attribute  "Input" . DefaultAttribute DefaultAttribute class can be used to specify a default value (using  "Default"  attribute) for an input parameter.  Bool [Input("Bool input")] [Output("Bool output")] [Default("True")] public InOutArgument<bool> Bool { get; set; } DateTime [Input("DateTime input")] [Output("DateTime output")] [Default("2013-07-09T02:54:00Z")] public InOutArgument<DateTime> DateTime { get; set; } Decimal [Input("Decimal input")] [Output("Decimal output")] [Default("20.75")] public InOutArgument<decimal> Decimal { get; set; } Double [Input("Double input")] [Output("Double
Read more

Get Workflow Guid in Javascript using OData query

I find that using workflow id might be problematic across deployment, so I wrote a function to retrieve workflow’s guid given the workflow’s name. However, please take some care in assigning workflow name to avoid pain. function call() {       alert("Tets"); var name="Create Phone Call Via Js"; alert(name); var wf=getWorkflowId(name); alert(wf);  } function getWorkflowId(workflowName) { var aa=workflowName; var entityId = Xrm.Page.data.entity.getId(); alert(entityId); alert(workflowName); var serverUrl = Xrm.Page.context.getClientUrl(); alert(serverUrl); var odataSelect = serverUrl + "/xrmservices/2011/OrganizationData.svc/WorkflowSet?$select=WorkflowId&$filter=StateCode/Value eq 1 and ParentWorkflowId/Id eq null and Name eq 'Create Phone Call Via Js'"; alert(odataSelect);     var xmlHttp = new XMLHttpRequest();     xmlHttp.open("GET", odataSelect, false);     xmlHttp.send();     if (xmlHttp.status ==
Read more

Convert Plugin to Sandbox mode,

While working with Dynamics CRM Plugins, the thumb rule for Plugin Registration is: If you are working with CRM On-Premise, use Plugin isolation mode as  None. If you are working with CRM Online, use Plugin isolation mode as  Sandbox. So, now the scenario is you are working on big implementation for CRM On Premise. Now your organization decides to move to CRM Online. The first task comes to mind is to move all the Plugins to Sandbox mode and see if they are still working considering running Plugin in sandbox comes with some  limitations  (such as you cannot access file system/registries/external assemblies/protocols/IP Addresses etc). To convert the Plugin assemblies to Sandbox mode, one option is to open Plugin Registration tool and convert the assemblies one by one which is a tedious task. The other simple option is do this by Customization.xml file. Below are the steps how to do that. Create a solution with all Plugin assemblies or use existing solution if already a
Read more