Start a new topic

oInd vs. oIndRecord

Can you expound a little on what the difference and relation is between oInd and oIndRecord in the BeforeIndividualRelationshipSave sub?

It seems like an oIndRecord is created even if it is a non-constituent record, but that oIndRecord doesn't seem to be reflected in the oInd object.  

My example here is setting the primary addressee/salutation.  If I set it on the oIndRecord it doesn't seem to come through on the oInd object.  So is the oIndRecord only useful when it is a relationship to a full constituent?

Also, it seems that for non-constituents when I look up oIndRecord.Spouse it is blank, even when they are the spouse record.  Is that again just a consequence of oIndRecord being a false object if it is a non-constituent?


The oIndRecord is a CRecord object and the oInd is the relationship object. Every relationship, full or non-constituent has a CRecord object. Some fields in the field mapping are only available on the CRecord so it is provided as well.

You won't see any changes you make to oIndRecord object showing up in the oInd object unless the oInd object is reloaded.

As for the spouse question. When you create a non constituent relationship in RE, there is only one relationship created, from the main to the non-constituent. When you create a relationship to a full constituent, there are two relationships created, from 1 to 2 and from 2 to 1. So when you look at a non-constituent spouse's .Spouse property you are asking RE to look for a relationship that doesn't exist. It only exists from the full constituent to the non-constituent
Thanks for the quick response Nic!
I finally figured it out!

If you are working with a CIndividual2 record linked to a non-constituent the CONSTIT_ID field is actually the ID of the primary record, the RELATION_ID field is the non-constituent record, and the RECIPRICAL_ID field is blank.
Login or Signup to post a comment