Back to Details

add-datasource

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
📋 Shared Instructions: shared-instructions.md - Cross-cutting concerns.
📋 通用说明：shared-instructions.md - 跨领域相关事项。

Add Data Source

添加数据源

Router skill that understands the user's goal and connects them to the right data source -- without requiring them to know Power Platform terminology.
这是一个路由技能模块，能够理解用户的目标，并将其连接到合适的数据源——无需用户了解Power Platform的专业术语。

Workflow

工作流程

Check Memory Bank

检查记忆库

Check for 
memory-bank.md
per shared-instructions.md.
根据shared-instructions.md检查
memory-bank.md
文件。

Understand the Goal

理解用户目标

  1. If 
    $ARGUMENTS
    is provided or the caller already specified what's needed    , use it directly and skip the question below.
  2. Otherwise, ask the user what they want their app to do -- not which connector to use. Focus on the end goal. Example questions:
    • "What kind of data does your app need to work with?"
    • "What should your app be able to do? (e.g., search company info, manage tasks, send messages)"
  3. Based on their answer, recommend the best approach and explain why it's the right fit. The user shouldn't need to know the difference between Dataverse, SharePoint, or other connectors -- that's our job.
  1. 如果提供了
    $ARGUMENTS
    参数，或者调用方已经明确了需求    ，则直接使用该参数，跳过下面的问题。
  2. 否则，询问用户他们希望应用实现什么功能——而不是问要使用哪个连接器。聚焦最终目标。示例问题：
    • "你的应用需要处理哪种类型的数据？"
    • "你的应用应该具备什么功能？（例如：搜索公司信息、管理任务、发送消息）"
  3. 根据用户的回答，推荐最佳方案并解释为什么它是合适的选择。用户不需要了解Dataverse、SharePoint或其他连接器之间的区别——这是我们的工作。

Route to the Right Skill

引导至合适的技能模块

Map the user's goal to the appropriate skill:
User's goalBest approachInvoke
Store and manage structured business data (custom tables, forms, CRUD)Dataverse is the platform's native database
/add-dataverse
Track work items, bugs, builds, or pipelinesAzure DevOps connector
/add-azuredevops
Send or read Teams messages, post to channelsTeams connector
/add-teams
Read/write Excel spreadsheet dataExcel Online (Business) connector
/add-excel
Upload, download, or manage filesOneDrive for Business connector
/add-onedrive
Work with SharePoint lists or document librariesSharePoint Online connector
/add-sharepoint
Send emails, read inbox, manage calendar eventsOffice 365 Outlook connector
/add-office365
Invoke an AI agent or copilot built in Copilot StudioCopilot Studio connector
/add-mcscopilot
Something else or not sureGeneric connector (we'll figure it out)
/add-connector
Important routing rules:
  • When the user wants to perform actions (send an email, post a message, create a file), use the specific connector for that action (e.g., 
    /add-office365
    for sending email, 
    /add-teams
    for posting messages).
  1. If the user wants multiple capabilities, invoke each skill in sequence.
将用户的目标映射到合适的技能模块：
用户目标最佳方案调用指令
存储和管理结构化业务数据（自定义表格、表单、CRUD操作）Dataverse是平台的原生数据库
/add-dataverse
跟踪工作项、Bug、构建或流水线Azure DevOps连接器
/add-azuredevops
发送或读取Teams消息、发布到频道Teams连接器
/add-teams
读写Excel电子表格数据Excel Online (Business)连接器
/add-excel
上传、下载或管理文件OneDrive for Business连接器
/add-onedrive
处理SharePoint列表或文档库SharePoint Online连接器
/add-sharepoint
发送邮件、读取收件箱、管理日历事件Office 365 Outlook连接器
/add-office365
调用Copilot Studio中构建的AI Agent或CopilotCopilot Studio连接器
/add-mcscopilot
其他需求或不确定通用连接器（我们会解决）
/add-connector
重要路由规则：
  • 当用户想要执行操作（发送邮件、发布消息、创建文件）时，使用对应操作的专用连接器（例如：发送邮件使用
    /add-office365
    ，发布消息使用
    /add-teams
    ）。
  1. 如果用户需要多种功能，依次调用每个技能模块。

When the User Isn't Sure

用户目标不明确时的处理

If the user describes a vague goal (e.g., "I need data for my app"), guide them:
  1. Ask what their app does and who uses it
  2. Ask what data they need to display or interact with
  3. Recommend the simplest approach that meets their needs
  4. Explain the recommendation in plain language (avoid jargon like "connector", "Dataverse", "tabular data source" unless the user uses those terms first)
如果用户描述的目标模糊（例如：“我的应用需要数据”），引导他们：
  1. 询问他们的应用功能是什么，以及用户群体是谁
  2. 询问他们需要显示或交互的数据类型
  3. 推荐满足需求的最简方案
  4. 用通俗易懂的语言解释推荐方案（避免使用“连接器”、“Dataverse”、“表格数据源”等行话，除非用户先使用这些术语）