无代码实现InfoPath表单提交数据至两个SharePoint列表可行性咨询

Absolutely! You can pull this off entirely without writing a single line of code—here's a step-by-step breakdown tailored to your needs:

1. 先准备两个SharePoint列表 #

First, set up your two lists with matching field types where needed:

• 列表A:
  • ReqID (单行文本，后续设为只读)
  • Description (多行文本)
  • User (人员或组字段)
  • Date (日期时间字段)
  • Testing (多行文本，设置为隐藏字段，不在用户视图中显示)
  • Tester (人员或组字段，同样设置为隐藏字段)
• 列表B:
  • ReqID (单行文本)
  • Description (多行文本)
  • Testing (多行文本)
  • Tester (人员或组字段)
  • Date (日期时间字段)

2. 设计InfoPath表单 #

• Add all required fields to your form: ReqID, Description, User, Date, Testing, Tester.
• Set the ReqID control to read-only so users can’t edit it (it’ll be auto-generated later).
• Bind each form field to the corresponding field in 列表A—including the hidden Testing and Tester fields (they’ll temporarily store data for the workflow).
• Configure the form’s primary submit action to send data directly to 列表A.

3. 配置自动工作流生成ReqID并同步到列表B #

Use SharePoint’s classic no-code workflow engine (it’s intuitive for this scenario):

• Go to 列表A > 设置 > 工作流设置 > 添加工作流.
• Choose the SharePoint 2013 Workflow template (or 2010 if that’s available), name it something like "Submit to Dual Lists", and set it to start automatically when a new item is created.
• Add your first workflow action: Update List Item
  • Select "Current Item" as the item to update.
  • Set the ReqID field to the value: "Req-" + ID (use the workflow’s string concatenation to combine the prefix with the list’s built-in auto-incrementing ID).
• Add a second workflow action: Create List Item
  • Select 列表B as the target list.
  • Map each field from 列表A to the corresponding field in 列表B:
    • ReqID: Use the updated ReqID from the current item
    • Description: Current item’s Description
    • Testing: Current item’s Testing
    • Tester: Current item’s Tester
    • Date: Current item’s Date
• Save and publish the workflow.

关键注意事项 #

• The hidden fields in 列表A are just a temporary storage trick—users won’t see them, but they let the workflow access the Testing and Tester values to pass to 列表B.
• If your environment uses Power Automate instead of classic workflows, you can replicate this logic there too: trigger on a new item in 列表A, update ReqID, then create an item in 列表B with the mapped fields.

Give this setup a test run by submitting a form—you should see 列表A populate with the auto-generated ReqID, and 列表B get a matching entry with all the required fields.

内容的提问来源于stack exchange，提问作者Nat85