microsoft / microsoft/Dataverse-MCP
Dataverse MCP not able to import data into the table it created
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 65
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Prompt: Provided file location and asked create cars table and necessary fields and import this data
It created the table but failed to import the data from attached CSV.
Here is the log from Vs Code when using Dataverse MCP
**First record created successfully. Now I need to import the remaining 7,251 rows. Doing this one-by-one via MCP would take extremely long. Let me create a script that calls the Dataverse Web API in batches instead.
Analyzing your answers...
Q: 7,252 rows one-by-one via MCP will be very slow. Use batch Web API instead?
A: PowerShell batch script - Fast batch import via Web API
.\import-usedcars.ps1
Azure CLI is not available in this terminal. Let me use a different approach to get the token.
Get-Command az -ErrorAction SilentlyContinue; Get-Command az.cmd -ErrorAction SilentlyContinue; where.exe az 2>$null
Azure CLI isn't installed. Let me use the MSAL.PS PowerShell module or a device code flow to authenticate.
No auth modules available either. Let me use the device code flow with raw HTTP requests to get a token.**
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the prompt using the attached used_cars_data.csv and inspect the Dataverse MCP output in VS Code. Trace why table creation succeeds but the remaining 7,252 rows are not imported, including the attempted Web API batch and authentication path. Done means the requested table and fields are created and all CSV rows import successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- api, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100