DXL新手求助：通过DOORS模块B实现模块A指定位置的数据更新合并

Hey there! Since you're new to DXL, let's walk through a practical, step-by-step solution for your module merge workflow. I'll break this down into actionable parts with code snippets you can adapt to your specific setup.

First, let's make sure your Excel changes are properly imported into Module B:

• Open DOORS, create a new Module B or use an existing empty one.
• Go to File > Import > Microsoft Excel and follow the import wizard.
  • Pro tip: Map Excel columns to DOORS attributes (like Object Text, a custom UniqueID, or other fields) that you’ll use later to match entries with Module A.
  • Double-check that any hierarchical structure in Excel translates correctly to Module B’s tree—this will simplify merging later.

This is the heart of the solution. The script will:

1. Locate your target position in Module A’s tree.
2. Loop through all entries in Module B.
3. Either update matching entries in Module A or insert new ones at your specified spot.

Here's a commented, beginner-friendly script you can tweak:

// 1. Open your modules (edit mode for A, read-only for B)
Module modA = edit("Module A", false) // Replace with your actual module name
Module modB = read("Module B")       // Replace with your actual module name

// 2. Define the target position in Module A (customize this to your needs)
// Example: Find the target by its object text (replace with your target's text)
Object targetPosition = find(modA, "My Target Parent Node")

// Error check: Make sure we found the target
if (null targetPosition) {
    print "Oops! Target position not found in Module A.\n"
    close(modA)
    close(modB)
    exit
}

// 3. Loop through every entry in Module B
Object bEntry = first(modB)
while (null != bEntry) {
    // Use a unique identifier to match entries (adjust to your attribute)
    string bUniqueID = bEntry."UniqueID" // Replace with your matching attribute

    // Check if this entry already exists in Module A
    Object aMatch = null
    for aEntry in entire modA do {
        if (aEntry."UniqueID" == bUniqueID && null != aEntry."UniqueID") {
            aMatch = aEntry
            break
        }
    }

    if (null != aMatch) {
        // Update existing entry: overwrite attributes with Module B's values
        print "Updating entry with ID: " bUniqueID "\n"
        aMatch."Object Text" = bEntry."Object Text"
        // Add more attribute updates here (e.g., custom fields, statuses)
    } else {
        // Insert new entry as a child of the target position
        print "Inserting new entry: " bEntry."Object Text" "\n"
        Object newEntry = create(targetPosition, below) // Use "below" for child, "after" for sibling
        newEntry."Object Text" = bEntry."Object Text"
        newEntry."UniqueID" = bUniqueID
        // Copy other attributes from Module B as needed
    }

    bEntry = next(bEntry)
}

// 4. Clean up and save changes
save(modA)
close(modA)
close(modB)
print "Merge completed successfully!\n"

• Target Position: Instead of finding by object text, you can locate the target using its absolute number (e.g., targetPosition = object(123, modA)), or a custom attribute. Adjust the find logic to fit your setup.
• Matching Criteria: If you don’t have a UniqueID attribute, use the default Object Identifier (note: this is module-specific) or combine multiple attributes (like Object Text + a version number) to avoid false matches.
• Tree Placement: Use create(targetPosition, before) or create(targetPosition, after) to insert as a sibling, instead of a child node.

• Always test scripts on copies of your modules first—DOORS doesn’t have an undo button for DXL changes!
• Use print statements to debug: add print "Processing: " bEntry."Object Text" "\n" to track what the script is doing.
• Explore DOORS’ built-in DXL Reference (Help > DXL Reference)—it’s your go-to for understanding objects, attributes, and tree operations.

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