Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X
If there are no relation in parameters of part and assembly, I think it should not matter which parameters are updating first..
Are you using EXECUTE statements?
If your parts have INPUT parameters, then you can use EXECUTE statements in your assembly to drive the INPUT parameters of the parts which are in your assembly.
You only have to regenerate your assembly once, the EXECUTE statements will do the rest. All your parts will update/regenerate.
Example:
a.assembly
INPUT
PART_1_HOLE YES_NO
PART_2_WIDTH NUMBER
PART_3_NAME STRING
END INPUT
RELATIONS
/* Make calculations, etc, at assembly level
END RELATIONS
EXECUTE PART PART1
HOLE = PART_1_HOLE
END EXECUTE
EXECUTE PART PART2
WIDTH = PART_2_WIDTH
END EXECUTE
EXECUTE PART PART3
NAME = PART_3_NAME
END EXECUTE
ADD PART PART1
...
END ADD
ADD PART PART3
...
END ADD
ADD PART PART3
...
END ADD
-----
Part1.prt
INPUT
HOLE YES_NO
END INPUT
etc.
-----
Part2.prt
INPUT
WIDTH NUMBER
END INPUT
etc.
-----
Part3.prt
INPUT
NAME STRING
END INPUT
etc.
Our models are driven bij 1200+ INPUT parameters (we use an Excel spreadsheet to calculate those 1200+ parameters). We drive a couple hundred parts, which contain up to 20.000 features.
In that case, we probably changed something in Excel (changed a width, enabled an option). So to revert back, we have to change the things in Excel back to the previous value and regenerate the assembly.