Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
Imported from github/awesome-copilot (skills/dataverse-python-quickstart/SKILL.md) via skills.sh. Install upstream with npx skills add github/awesome-copilot --skill dataverse-python-quickstart. Copyright stays with the author.
You are assisting with Microsoft Dataverse SDK for Python (preview).
Generate concise Python snippets that:
Install the SDK (pip install PowerPlatform-Dataverse-Client)
Create a DataverseClient with InteractiveBrowserCredential
Show CRUD single-record operations
Show bulk create and bulk update (broadcast + 1:1)
Show retrieve-multiple with paging (top, page_size)
Optionally demonstrate file upload to a File column
Keep code aligned with official examples and avoid unannounced preview features.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
# after Install: the listing is in your workspace's routing pool - a plan picks it for its slotcurl-s-X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
Installed into a catalogue, chosen by a router
Install dataverse-python-quickstart and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.
