在创建实体时编辑CRM实体。 CRM Dynamics插件

Question

I have a CRM custom plugin that is registered (via CRM Plugin Registration Tool) on the event Create Job. 'Create' being the message and 'job' being the Primary Entity.

Upon creation of a new job, I want to take that entity and automatically assign it a project number. I always set the 'Event Pipeline Stage of Execution' to be Post-Operation. I have tried both Execution Modes (Asynchronous and Synchronous).

Asynchronous always throws me an error along the lines of "Entity job with ID '' does not exist"

Synchronous never throws an error but none of the code within my tool is being performed.

    public void Execute(IServiceProvider serviceProvider)
    {
        var factory = (IOrganizationServiceFactory)serviceProvider.GetService(typeof(IOrganizationServiceFactory));
        var orgService = factory.CreateOrganizationService(null);
        var context = (IPluginExecutionContext)serviceProvider.GetService(typeof(IPluginExecutionContext));        
        Entity ent = (Entity)context.InputParameters["Target"];

        IOrganizationService service = factory.CreateOrganizationService(null);
                    if (ent.LogicalName == "cmc_job")
        {
            try
            {                   
                ent["cmc_jobnumber"] = "0000001";
                ent["cmc_name"] += " - DEMO";
                service.Update(ent);                    
            }
            catch (Exception e)
            {
                Console.Write(e.Message);
            }

    }

I have also tried service.Create(entity) as well but I tend to run into errors with that as well. These errors often relate to having duplicate records. Also I have made sure to deactivate any existing processes that relate to creating jobs.

How can I properly update an entity field immediately after creating the entity? Which practice is best?

Side Note : The reason I am deciding to use a CRM Custom Plugin and not a custom Processes is because I need to query out the largest existing project number and then adding 1 to it.

Answer 1

For an auto-numbering plugin, the best practice is to register on Pre-Operation (Synchronous). This way the auto-numbered fields will be set within the same database transaction that creates the record (avoiding unnecessary transactions and messy audit history).

When writing pre-operation plugins, you should not call service.Update(), but simply set the values on the target (as you currently are), and they will be persisted along with the other attributes of the target. Comment out your service.Update() line and your plugin should work on pre-operation.

Asynchronous always throws me an error along the lines of "Entity job with ID '' does not exist

Synchronous never throws an error but none of the code within my tool is being performed

This happens because during create an ID is not assigned to records until they are persisted to the database. You are taking the Target (which has no ID) and then attempting to perform a service.Update() which expects an entity with an ID. Both sync and async calls will throw an error, but the async error happens in the background and you don't see it.

Answer 2

You have to recheck with asynchronous step registration in PRT.

Whenever you are accessing the just created record Id in post message pipeline, sync plugin will fail as the DB transaction is not yet committed.

But asynchronous plugin will succeed as the DB transaction is committed & record by Id is accessible.

Anyway the best practice is set the needed attribute value in pre-operation itself to avoid another explicit update service call. You can find lot of similar accepted answers with the same suggestion in SO itself, also in Dynamics community & internet blogs.