When using an OIR that assigns a new sequence number for an IBA, the IBA is only populated during a Create operation, but doesn't get a new sequence number on a SaveAs operation. This causes problems since customers expect that sequence number to be unique across objects. An example is the following. Customer wants an IBA, named Graphic ID, to hold a unique number for each graphic object in the system. Whether a graphic is created from scratch or using the SaveAs, this Graphic ID needs to be unique. Currently, if a SaveAs is performed on a graphic object, both end up having the same Graphic ID value.