Yes, the RegisterForeignKey method would be a great option here. The RegisterForeignKey method allows you to create as many foreign relationships as you need to any one (or multiple) BOs. This is the purpose for this method. The only difference from the single ParentBusinessobject funtionality is that when you adda new record, you must set the foreign key field's value (even if it is a new negative PK value) and then the RegisterForeignKey logic will handle everything else from there. Just to illustrate my point:MyParentBO.ForeignKeyField = MyInitialValue