如何在SharePoint 2010中创建按条件跨列表迁移数据的简单工作流

Got it, let's walk through exactly how to build this cross-list data migration workflow for your scenario. I’ll break it down into actionable steps that work for most site-based list platforms (like SharePoint, Power Platform, etc.):

First, you need to define clear rules for which ACTION values trigger migration to which lists. For example:

• If ACTION = "Archive", migrate to List2
• If ACTION = "Escalate", migrate to List3 (if you have multiple target lists)
  Write this mapping down—this will be the core logic driving your workflow.

You need a workflow trigger that fires the moment a new item is created in List1. Most platforms have built-in triggers for this:

• In SharePoint: Use Power Automate (or SharePoint Designer if you prefer classic workflows)
• In low-code platforms: Look for a "When an item is created" trigger in the automation section

Once the trigger activates, add a Condition action to compare the new item's ACTION field against your predefined static values.

• Configure the condition to check: List1 > ACTION equals [your target value, e.g., "Archive"]
• Add multiple condition branches if you need to handle multiple target lists (one branch per list)

For each condition branch that evaluates to true:

• Add a "Create item" action pointing to your target list (e.g., List2)
• Map the source fields from List1 to the corresponding fields in the target list:
  • SID → LSID
  • ORG → LORG
  • ACTION → LACTION
  • PATTERN → LPATTERN
    Double-check that data types match between source and target fields (text to text, number to number) to avoid migration errors.

If you don’t want to keep a copy of the item in List1 after migration, add a "Delete item" action right after the "Create item" step. Target the newly created List1 item using its unique ID.

If you’re using Power Automate with SharePoint, your flow will look something like this:

1. Trigger: When an item is created (Site Address: Your Site, List Name: List1)
2. Condition: TriggerBody()?['ACTION'] equals 'Archive'
3. If Yes:
   • Action: Create item (Site Address: Your Site, List Name: List2)
     • LSID: TriggerBody()?['SID']
     • LORG: TriggerBody()?['ORG']
     • LACTION: TriggerBody()?['ACTION']
     • LPATTERN: TriggerBody()?['PATTERN']
   • (Optional) Action: Delete item (Site Address: Your Site, List Name: List1, Item ID: TriggerBody()?['ID'])
4. If No:
   • Add other branches for different ACTION values, or leave as "Do nothing"

• Field Mapping Issues: Verify that you’re using internal field names (not just display names) — in SharePoint, you can find these via List Settings → Column Settings → Check the URL for the field’s internal name.
• Permission Errors: Make sure the workflow has edit permissions on both List1 and all target lists.
• Test First: Create a test item in List1 with your target ACTION value to confirm the workflow runs and migrates the item correctly.

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