CDS "Update a record" Action is different when Flow is created Inside vs Outside a Solution

[LATest]

Basically I need to Update another record, with the Name of the Entity and Attributes (and values) to be updated being provided from JSON.  I can get the logic I want to work when I create a Flow outside of a CDS Solution. 

However, I need the flow to trigger on both Create and Update, and to do this I need to create the Flow within a CDS Solution as the Trigger on Create and Update is only available inside a flow created from inside a CDS Solution.

The problem I have is that on a later step in the flow when I want to update a CDS record the "Update a record" action when I choose "Enter custom value" for the Entity name (need to enter a custom value as the name is being provided from JSON), another field is required

• For a Flow created outside a CDS Solution the field is called "Body" (and I can put attibute:value pairs in it).  
• For a Flow created inside a CDS Solution the field is called "Item" (and I cannot even save the Flow)

When I peak the code for both I see

"body": {
            "myname": "xxs_test"
        },

vs 
    "parameters": {
            "dataset": "orgxxxxxxxx.crm6",
            "table": "@outputs('Update_a_record')?['body/xxx_name']",
            "id": "xxxxxxxxxxxxxxxxxxxxx",
            "undefined": {
                "myname": "xxs_test"
            }
        },

For the Flow created inside a Solution, when I attempt to Save the Flow it it throws an error to it not being able to handle 'Undefined'.  How can I add dynamics attributes and values ?

[PowerBack19]

@LATest - Have you tried using the Date Operation of "Parse JSON"? Here is an article outlining the usage: https://spmaestro.com/handling-json-in-microsoft-flow/

[LATest]

 @PowerBack19 The data that I am providing is going automatically in to "undefined", if I Parse JSON first it just places the JSON inside "Undefined".  

If I update a value on a selected Entity (rather than a Enter custom value), I see the following ("item/name" where name is the field being updated). 

"parameters": {
            "dataset": "orgxxxxxx.crm6",
            "table": "accounts",
            "id": "@triggerOutputs()?['body/accountid']",
            "item/name": "xxxxxxx",

But when I do "Enter custom value" I cannot get keys and values into the "Parameters" (Note: The "Parameters" main structure is being provided by the Update a record Action itself), the only field that I get to add my value into appears to automatically nest my key(s)/value(s) under a key labeled "undefined", and then on Save it then throws an error because it doesn't like "undefined":

Request to XRM API failed with error: 'Message: Flow client error returned with status code "BadRequest" and details "{"error":{"code":"InvalidOpenApiFlow","message":"Flow save failed with code 'WorkflowOperationParametersExtraParameter' and message 'The API operation does not contain a definition for parameter 'undefined'.'."}}"

The really frustrating thing with this is I can get it to do what I want if the Flow is created outside a CDS Solution (but then I don't get the Create and Update trigger that I am after). And I am using exactly the same CDS Update a record Action in both cases (but it appears to not behave the same).

[abm]

Hi @LATest 

Could you please post the details of the error and a screenshot of your flow?

You can determine the SDK message whether it's create, update or delete using the expression 

triggerOutputs()?['body/SdkMessage']. This SDKMessage is not available under the Dynamic content mappings.  Construct this under the expression. See below.

Hopefully you don't need to create two types of flow anymore. Using the above technique SDKMessage property returns Create, Update or Delete operation types.

Thanks 

[LATest]

@abm I am missing as to why I would need trigger/body - the issue isn't related to the Trigger component, but further down the flow when I want to update a different record I cannot save the Flow (inside the Flow editor).

On the Step where being unable to save error occurs I am using an CDS "Update a record" Action but rather than selecting an Entity Name from the list, I am choosing "Enter custom value", I add the Entity Name from JSON this then gives me an extra mandatory value called "body"

Whatever I have tried putting in 'Body' (text, JSON object), creates a parameter called 'undefined' (with my entered value nested inside it) as per my previous posts,  but when I press Save an SDK error gets thrown.

Request to XRM API failed with error: 'Message: Flow client error returned with status code "BadRequest" and details "{"error":{"code":"InvalidOpenApiFlow","message":"Flow save failed with code 'WorkflowOperationParametersExtraParameter' and message 'The API operation does not contain a definition for parameter 'undefined'.'."}}". Code: 0x80060467 InnerError: Type: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=9.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]] Message: Flow client error returned with status code "BadRequest" and details "{"error":{"code":"InvalidOpenApiFlow","message":"Flow save failed with code 'WorkflowOperationParametersExtraParameter' and message 'The API operation does not contain a definition for parameter 'undefined'.'."}}". StackTrace: at Microsoft.Crm.Extensibility.OrganizationSdkServiceInternal.Update(Entity entity, InvocationContext invocationContext, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode, Boolean checkForOptimisticConcurrency, Dictionary`2 optionalParameters) at Microsoft.Crm.Extensibility.OData.CrmODataExecutionContext.Update(Entity entity, UpdateOption updateOption) at Microsoft.Crm.Extensibility.OData.CrmODataServiceDataProvider.UpdateEdmEntity(CrmODataExecutionContext context, String edmEntityName, String entityKeyValue, EdmEntityObject entityObject) at Microsoft.Crm.Extensibility.OData.EntityController.PatchEntityImplementation(String& entityName, String key, EdmEntityObject entityDelta) at Microsoft.Crm.Extensibility.OData.CrmODataUtilities.<>c__DisplayClass10_0`2.<InvokeActionAndLogMetric>b__0() at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute[TResult](ILogger logger, EventId eventId, ActivityType activityType, Func`1 func, IEnumerable`1 additionalCustomProperties) at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute[TResult](ILogger logger, XrmTelemetryActivityType activityType, Func`1 func) at lambda_method(Closure , Object , Object[] ) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Dispatcher.HttpControllerDispatcher.<SendAsync>d__1.MoveNext() InternalException: '.

(I can get this to work if the Flow is created outside a CDS Solution, in this case rather than "Body", the mandatory field is "Item" and it accepts a JSON object and it represents the Body payload rather than a nested parameter called 'unknown'.  But outside a CDS Solution I don't have a Create + Update combined Trigger and so would have to create a Flow for Create and another for Update with exactly the same logic other  than the initial Trigger).

[abm]

Hi @LATest 

There are some differences between two CDS connectors. Which CDS connector are you using? Also you mentioned you can save this outside the solution. Could you post a screenshot of your JSON schema? 

Thanks

[LATest]

@abm Yes, I am aware there are two CDS component sets (this is also confusing from Microsoft as the components are named the same but also return different formatted results for the List Records action - but that's a side issue), I have tried the "Update a record" from both and get the same Save error.

JSON 'entity' contains the name of an entity e.g. "new_test", I also make use of the same JSON "entity" in a CDS List Records action earlier in the Flow and that runs successfully (I also pull another item from the JSON that is used in constructing the filter for the List Records - the general JSON stuff is ok).

For the "Update a record" action when I "peek the code" on one where I select an entity from the list I get 

"parameters": {
            "entityName": "accounts",
            "recordId": "475b158c-541c-e511-80d3-3863bb347ba8",
            "item/name": "xxxxxxxx"
        },

vs for "Enter custom value"

"parameters": {
            "entityName": "@items('Apply_to_each_Entities')?['entity']",
            "recordId": "475b158c-541c-e511-80d3-3863bb347ba8",
            "undefined": {
                "name": "xxxxxx"
            }

The error message on Save is saying it doesn't like "undefined"

'The API operation does not contain a definition for parameter 'undefined'.'

The difference between the 2 blocks above (apart from the dynamic value in entityName) is there's a keyword called "undefined" in "parameters".   (the keyword "name" is coming from my entry in the 'Body" input box and its the same error if I put "items/name", text or a JSON object in the 'Body' input box - always nests it under "undefined"). 

So in my mind either 'undefined' shouldn't be there or there is a special structure that is required to be nested under it (or Custom value doesn't work - but I know it does work if the flow is created outside a CDS Solution but in that case the content when you peek the code goes in a "body" rather than in "paramaters->undefined")