CREATE DYNAMICS 365 ENTITY IN SDK

In this post, we will learn how to create a Dynamics 365 custom entity in SDK and how to set some of its properties.

  1. The below function can be used to create a custom entity

    public void CreateEntity()
    {
    CreateEntityRequest createrequest = new CreateEntityRequest
    {
    Entity = new EntityMetadata
    {
    SchemaName = "cak_CustomEntity",
    DisplayName = new Label("Custom Entity", 1033),
    DisplayCollectionName = new Label("Custom Entities", 1033),
    Description = new Label("Custom entity created using SDK", 1033),
    OwnershipType = OwnershipTypes.UserOwned,
    IsActivity = false,
    IsBusinessProcessEnabled = true,
    IsAuditEnabled = new BooleanManagedProperty(true),
    IsSLAEnabled = false,
    },
    PrimaryAttribute = new StringAttributeMetadata
    {
    SchemaName = "cak_name",
    RequiredLevel = new AttributeRequiredLevelManagedProperty(AttributeRequiredLevel.None),
    MaxLength = 100,
    FormatName = StringFormatName.Text,
    DisplayName = new Label("Name", 1033),
    Description = new Label("Primary attribute for the custom entity.", 1033)
    },
    HasActivities = true,
    HasNotes = true,
    SolutionUniqueName = "CAK",
    };
    try
    {
    var result = AdminService.Execute(createrequest);
    if (result.Results != null)
    Console.WriteLine("Custom Entity successfully created!");
    }
    catch (Exception e)
    {
    Console.WriteLine($"Error while creating the custom entity. \n\rError message: {e.Message}");
    }
    }

  2. Based on your needs, you can add or remove the properties you want to set for the entity you want to create or its primary field
    Create entity request 1

    Create entity request 2

  3. If you want to add the created entity to a specific unmanaged solution, you can set the solution name accordingly in the SolutionUniqueName property
    Create entity request 3

Hope This Helps!

Comments

Post a Comment

Popular posts from this blog

DYNAMICS 365 HOW TO HIDE RECENT RECORDS FOR LOOKUP FIELD IN UCI

Image
In UCI, a lot of behaviors have been changed comparing to the Classic Web Interface such as the tabs, BPF, and many others. Today, I will be talking about one of these behaviors which is the Recent Records in lookup fields. In a brief summary, the Recent Records feature will suggest the latest records that have been searched for, where the user can select one of them, and, the list of available records of the current view will then be displayed. This is a nice-to-have feature since it might help the users to speed up data entry. However, if the lookup has been filtered to display specific records, the Recent Records will not respect this filter and will keep showing records even is they should not. This scenario can lead to selecting a record by the user that is not allowed to be selected. Therefore, in this situation, it is better to hide the Recent Records t
Read more

SEARCH BY GUID IN DYNAMICS 365

Image
Is it possible to search for a CRM record using its GUID ? Well, NO it is not possible and YES it is possible!!! As always has been, it is not possible to search for a record by its guid in Advanced Find and in the Quick view search. However, in the model-driven app Edit filters functionality, it is possible to search for a record by its Guid. How it works, let's check the 3 different places where we can search for a records. Advanced Find search Using the Advanced find feature, you cannot put a GUID value to search for. You will directly receive an error notification eventhough when you download the fetchXml, the Guid of the record will be there. Quick view search Using the search box
Read more

SAVE FORM IN DYNAMICS 365 JAVASCRIPT

Image
In Dynamics 365, you may need to save a CRM form automatically in JavaScript upon a specific action on the form. In order to do that, the function formContext.data.save(saveOptions).then(successCallback, errorCallback); can be used to save the record asynchronously with callback functions to be executed after the save operation is completed. The following example will display a successful message if the save operation is completed, and a failure message if not. formContext.data.save(1).then( function () { alert("Successfully Saved!"); }, function () { alert("Failed while saving!"); });
Read more