[Bug] Dataverse Common Service connector doesnt work as data source.

[TomasCaruso10]

Describe the bug

Im trying to upload a file from a code app, this feature its not supported using add-data-source -a dataverse -t ...
So, i added de shared common service connector to the app as it was a custom connector.
The sdk generated all the methods, i had noted that using non organization specific methods dosent work, so i try this one..

`
/**

• Upload a file or an image to selected environment
• Update file or image content in a row in a Power Platform environment.
  */
  public static async UpdateEntityFileImageFieldContentWithOrganization(content_type: string, organization: string, entityName: string, recordId: string, fileImageFieldName: string, item: string, x_ms_file_name: string): Promise<IOperationResult> {
  const params: { content_type: string, organization: string, entityName: string, recordId: string, fileImageFieldName: string, item: string, x_ms_file_name: string } = { content_type, organization, entityName, recordId, fileImageFieldName, item, x_ms_file_name };
  const result = await MicrosoftDataverseService.client.executeAsync<{ content_type: string, organization: string, entityName: string, recordId: string, fileImageFieldName: string, item: string, x_ms_file_name: string }, void>(
  {
  connectorOperation: {
  tableName: MicrosoftDataverseService.dataSourceName,
  operationName: 'UpdateEntityFileImageFieldContentWithOrganization',
  parameters: params
  },
  });
  return result;
  }
  `
  The problem is that the sdk, is sending a bad request to the invoke endpoint, so im getting a 400 error.
  {
  "error": {
  "code": "0x80048d19",
  "message": "Error identified in Payload provided by the user for Entity :'', For more information on this error please follow this help link https://go.microsoft.com/fwlink/?linkid=2195293 ----> InnerException : Microsoft.OData.ODataException: A top-level property with name 'item' was found in the payload; however, property and collection payloads must always have a top-level property with name **'value'.\r\n

to debug this, i call the connector endpoint myself (without invoke) and the following request succeeded..

curl --location --request PUT 'https://bbeae572-ff04-e89b-89b1-d91671b42ae9.10.common.brazil.azure-apihub.net/apim/commondataserviceforapps/shared-commondataser-fakeid.../api/data/v9.1.0/tcs_documentos(9a7781a3-68cc-f011-8544-002248364293)/tcs_file?x-ms-file-name=postman.pdf' \ --header 'Authorization: Bearer eyJ0e....' \ --header 'content-type: application/octet-stream' \ --header 'Cookie: ... --data '{"item":"JVBERi0xLjQKJZOMi54gUmVwb3J0TGFiIEdlbmVyYXRlZCBQREYgZG9jdW1lbnQgaHR0cDovL3d3dy5yZXBvcnRsYWIuY29tCjEgMCBvYmoKPDwKL0YxIDIgMCBSCj4"}'

Also, i try debuggin with a simple update operation using this function:
public static async UpdateRecordWithOrganization(prefer: string, accept: string, organization: string, entityName: string, recordId: string, item: Record<string, unknown>, x_ms_odata_metadata_full?: boolean): Promise<IOperationResult<Record<string, unknown>>> { const params: { prefer: string, accept: string, organization: string, entityName: string, recordId: string, item: Record<string, unknown>, x_ms_odata_metadata_full?: boolean } = { prefer, accept, organization, entityName, recordId, item, x_ms_odata_metadata_full }; const result = await MicrosoftDataverseService.client.executeAsync<{ prefer: string, accept: string, organization: string, entityName: string, recordId: string, item: Record<string, unknown>, x_ms_odata_metadata_full?: boolean }, Record<string, unknown>>( { connectorOperation: { tableName: MicrosoftDataverseService.dataSourceName, operationName: 'UpdateRecordWithOrganization', parameters: params }, }); return result; }

this also fails, beacuse the property "item" is added to the payload.
curl ^"https://bbeae572-ff04-e89b-89b1-d91671b42ae9.10.common.brazil.azure-apihub.net/invoke^" ^
-H ^"accept: application/json, application/json^" ^
-H ^"accept-language: es-ES^" ^
-H ^"authorization: Bearer eyJ0..." ^
-H ^"x-ms-client-app-id: /providers/Microsoft.PowerApps/apps/local^" ^
-H ^"x-ms-request-method: PATCH^" ^
-H ^"x-ms-request-url: /apim/commondataserviceforapps/shared-commondataser-827cb6b7-680c-4d0f-aeaf-17690ee343eb/api/data/v9.1.0/tcs_documentos(9a7781a3-68cc-f011-8544-002248364293)^" ^
-H ^"x-ms-user-agent: PowerApps/3.25111.8 (Web Player; AppName=local)^" ^
--data-raw ^"^{^^"item^^":^{^^"tcs_nombre^^":^^"Chefs-y-Primeros-Chefs.pdf^^",^^"tcs_id^^":^^"35-1011.00^^"^}^}^"

"message": "Error identified in Payload provided by the user for Entity :'', For more information on this error please follow this help link https://go.microsoft.com/fwlink/?linkid=2195293 ----> InnerException : Microsoft.Crm.CrmException: Invalid property 'item' was found in entity

Cloning that request into postman, and removing the "items" property, solves the issue.

Steps to Reproduce

1. add dataverse (shared_common_service) connector and let the sdk generate the service.
2. Call any of the above described methods.
3. See the bad request error.

Expected behavior

The common data service connector should work as any other custom connector y code apps..

Actual behavior

it dosent work.

[TomasCaruso10]

To accomplish the task of uploading a file from the code app, i found this alternative path:

• Create a custom api in dataverse that takes "item" as param.
• Create a power automate flow that triggers on that api call.
• Edit the sdk generated method for calling unbound actions to takl a string as item, instead of an object, because custom api does not allow to use objects.
• call the action.

`public static async uploadFile(
recordId: string,
fileName: string,
base64: string,
): Promise<IOperationResult<Record<string, unknown>>> {

// const client = getClient(dataSourcesInfo);

const result = await MicrosoftDataverseService.PerformUnboundActionWithOrganization(
  "https://org53b480dd.crm2.dynamics.com",
  "tcs_UploadFileToDataverse",
  JSON.stringify({
    "content_type": "application/octet-stream",
    "organization": "https://org53b480dd.crm2.dynamics.com",
    "entityName": "tcs_documentos",
    "recordId": recordId,
    "fileImageFieldName": "tcs_file",
    "x_ms_file_name": fileName,
    "base64": base64
  })
)
console.log(result);

return result;

}
`

i cant explain how anyoying is to do this while looking at the beautifull servive with all the methods i can ever possible need, and cant be 100% sure if its a bug, or im dooing something wrong..
why the hell can the sdk call custom connectors but cant call de dataverse connector.

[eschavez]

Hi @TomasCaruso10 – Thanks for raising this!

We currently do not support connecting to dataverse via the connector. Our current focus has been on achieving parity with Canvas Apps and enabling native Dataverse APIs for data access.

You can find guidance on connecting to Dataverse using these APIs here: Connect your code app to Dataverse.

We’ve noted your scenario and will review how we can support it in future updates. Appreciate your feedback!

[TomasCaruso10]

Hi, thanks for the clarification!

I started by following the documentation, and noticed that the generated SDK client exposes the following methods:

export type DataClient = {
    createRecordAsync: <TInput, TResult>(tableName: string, record: TInput) => Promise<IOperationResult<TResult>>;
    updateRecordAsync: <TInput, TResult>(tableName: string, recordId: string, changes: TInput) => Promise<IOperationResult<TResult>>;
    deleteRecordAsync: (tableName: string, recordId: string) => Promise<IOperationResult<void>>;
    retrieveRecordAsync: <TResult>(tableName: string, recordId: string, operation?: IOperationOptions) => Promise<IOperationResult<TResult>>;
    retrieveMultipleRecordsAsync: <TResult>(tableName: string, options?: IOperationOptions) => Promise<IOperationResult<TResult[]>>;
    executeAsync: <TRequest, TResult>(operation: IDataOperation<TRequest>) => Promise<IOperationResult<TResult>>;
};

For my scenario, I need to upload a document into a Dataverse column of type file.
To do that, I must call the Dataverse action UpdateEntityFileImageFieldContent.

My first attempt was to use the generic executeAsync method to invoke this operation, but this approach did not work.
Because of that, I added the Shared Common Service Connector as a “connection-type” data source to use the generated method instead.

However, if executeAsync is not intended for this kind of operation, this is a bit confusing — especially because the SDK-generated method for the connector is using the exact same executeAsync approach:

/**
 * Upload a file or an image to selected environment
 * Update file or image content in a row in a Power Platform environment.
 */
public static async UpdateEntityFileImageFieldContentWithOrganization(...) {
    const params = { ... };
    const result = await MicrosoftDataverseService.client.executeAsync(
      {
        connectorOperation: {
          tableName: MicrosoftDataverseService.dataSourceName,
          operationName: 'UpdateEntityFileImageFieldContentWithOrganization',
          parameters: params
        },
      });
    return result;
}

This suggests that, in theory, the generic executeAsync should be capable of executing this type of Dataverse action as well.

If this is not a bug, then enabling this functionality would unlock dozens of extremely useful Dataverse operations through the same interface, which would be a significant improvement for code apps.

Hope this helps clarify the scenario, and I hope you can consider supporting it!

Additional findings

I also tried using the Shared Common Service Connector with the following action:

/**
 * Perform an unbound action in selected environment
 * Run a global Dataverse action in a Power Platform environment, including custom actions.
 */
public static async PerformUnboundActionWithOrganization(
  organization: string,
  actionName: string,
  item?: string
): Promise<IOperationResult<Record<string, unknown>>> {
    const params = { organization, actionName, item };
    const result = await MicrosoftDataverseService.client.executeAsync(
      {
        connectorOperation: {
          tableName: MicrosoftDataverseService.dataSourceName,
          operationName: 'PerformUnboundActionWithOrganization',
          parameters: params
        },
      });
    return result;
}

The problem is that this action wraps everything inside a top-level item: {} object, and Dataverse’s file upload action does not accept that structure, so the operation fails.

To work around this limitation, I had to:

Create a custom Dataverse action that accepts all required parameters inside a single string under item, and

Create a Power Automate flow that receives this string, unpacks it, and calls the real Dataverse file upload action.

// CALL UNBOUND ACTION (Custom API -> Power Automate Flow)
  public static async uploadFile(
    recordId: string,
    fileName: string,
    base64: string,
  ): Promise<IOperationResult<Record<string, unknown>>> {

    const result = await MicrosoftDataverseService.PerformUnboundActionWithOrganization(
      "https://org..........crm2.dynamics.com",
      "tcs_UploadFileToDataverse",
      JSON.stringify({
        "content_type": "application/octet-stream",
        "organization": "https://org..........crm2.dynamics.com",
        "entityName": "tcs_documentos",
        "recordId": recordId,
        "fileImageFieldName": "tcs_file",
        "x_ms_file_name": fileName,
        "base64": base64
      })
    )
    console.log(result);

    return result;
  }

With this workaround, everything is “one step away” from working natively.

Final note

This feature is incredibly powerful — and with a small adjustment (allowing executeAsync to call Dataverse actions without enforcing the item wrapper), it could genuinely become a game changer for pro developers building Power Platform Code Apps.

Thanks again for reviewing this scenario, and I hope this helps show why enabling this capability would unlock a lot of value!