In the load combination options, users can custom define loads.

The combination ordering is specific to the entries - the rows at the bottom can use previous combinations above, but not v/v. AutoPIPE generates an error if a load case tries to reference loads towards in lower rows.

If a user wants to include a new load case in an existing definition, there is no way to "insert" a new load into the hierarchy or re-sort the existing load combinations.

Our only work around is to delete all of the load cases, and start again in order to retype/reselect everything.