[Bug] Dataverse table alias is ambiguous and native CRUD returns OperationNotFound

[carloshm]

Describe the bug

The documented tabular Dataverse command cannot be selected with Managed Apps CLI 0.23.0. The repository documentation says to use --connector dataverse --as table, but the CLI resolves dataverse to two connectors with the same display name and exits as ambiguous. Binding tables through shared_commondataserviceforapps succeeds, but native getClient(dataSources) CRUD calls then fail in App Player with OperationNotFound.

Steps to Reproduce

1. Create or initialize a Managed App in an environment with Dataverse.
2. Create a custom Dataverse table, for example sample_order.
3. Run:

ms app add data-source `
  --connector dataverse `
  --as table `
  --table sample_order `
  --skip-codegen `
  --non-interactive `
  --json

4. The CLI exits with:

Multiple connectors match 'dataverse'. Specify the connector ID directly:
  shared_commondataservice  (Microsoft Dataverse)
  shared_commondataserviceforapps  (Microsoft Dataverse)

5. Use the current-environment connector as a workaround:

ms app add data-source `
  --connector shared_commondataserviceforapps `
  --as table `
  --dataverse-environment-id <environment-id> `
  --table sample_order

6. Call native CRUD from the app:

const client = getClient(dataSources)
await client.createRecordAsync('sample_order', record)

Expected behavior

--connector dataverse --as table should resolve the dedicated tabular Dataverse data source described in plugins/microsoft-managed-apps/shared/connector-reference.md, bind the active environment without a connection ID, and generate metadata that native CRUD can execute.

Actual behavior

The alias is ambiguous because ms connector list exposes only shared_commondataservice and shared_commondataserviceforapps, both named Microsoft Dataverse.

Using shared_commondataserviceforapps generates a Dataverse table entry and dataset binding, but App Player native CRUD fails before reaching Dataverse:

{
  "error": {
    "path": "",
    "source": "configuration",
    "message": "Unable to match incoming request to an operation.",
    "reason": "OperationNotFound"
  }
}

The generated connector metadata has an empty version, so native CRUD constructs a dataset/table URL for which the runtime cannot match an operation. The failure affects both createRecordAsync and the preceding retrieveRecordAsync reconciliation calls.

Environment information

• Managed Apps CLI: 0.23.0 (latest npm dist-tag on September 10, 2026)
• Node.js: v26.7.0
• npm: 11.19.0
• OS: Windows
• Framework: React 19, TypeScript, Vite 8
• Connector: Microsoft Dataverse
• Enterprise network: Yes

Additional context

The repository documentation currently states that the tabular Dataverse connector is --connector dataverse and does not use the connection-id model. That command is not reachable unambiguously in CLI 0.23.0. shared_commondataservice exposes legacy tabular operations such as PostItem_V2, while shared_commondataserviceforapps exposes current-environment actions such as CreateRecord; neither provides the documented dedicated connector identifier through ms connector list.

[carloshm]

Additional findings from the same reproduction:

• Adding both Dataverse connectors as actions causes a code-generation name collision because both use the display name Microsoft Dataverse and generate generated/services/MicrosoftDataverseService.ts. The second generation overwrites the first; generated table services then reference methods that no longer exist.
• A working application-side workaround is to keep only shared_commondataservice and invoke its allowed GetItem_V2, PostItem_V2, and PatchItem_V2 operations through getClient(dataSources).executeAsync, supplying dataset and entity set explicitly. The generated paths are /{connectionId}/v2/datasets/{dataset}/tables/{table}/items[/{id}].
• The shared_commondataserviceforapps connection remains usable independently by a solution-aware Power Automate flow; removing its Managed App data-source binding does not remove the Power Platform connection or flow connection reference.