The Relation object relates users to interest groups, mailing lists and websites.
The Relation object also relates contacts to locations and organizations based on date range.
Applies to: Contacts, Interest Groups, Organization Members, Location Administrators, Organization Divisions. May be used for any relationship between items.
Relation.RelationID (UniqueID for Data Object)
Relation.ParentID (A site, a location, an organization, a group, a family, a parent)
Relation.ChildID
Relation.RelationTypeID (Role of child: Daughter, Step-Daughter, Member within group, etc.)
Relation.RelationTitle (Custom title of child within relationship. ie. My daughter)
Relation.
Status
0 = pending (not yet receiving)
1, 2 and 3 receive group emails.
1 = Active
2 = Active - Action required by moderator (to review new addition to group).
3 = Active - Action required by person being assigned (to accept group membership).
Relation.Access (Same as website
Access Levels)
Probably changing default from 0 to 1.
Relation.Priority (1=primary, 2+ Secondary relations between items.)
Relation.StartDate (nullable)
Relation.EndDate (nullable)
Relation.Creator
Relation.CreateDate
Relation.Modifier
Relation.ModifyDate
Lower numbered TypeID's are the parents of higher numbers
within relationships. As a result, it is typically not necessary to
represent each relationship two-ways in the RELATION table.
Sample drill-down hierarchy:
0 - Website
10000 - Location listed within website
20000 - Event at the location
30000 - Organization involved with the event
40000- Group within the organization
50000 - Vehicles
60000 - Individuals
70000 - Plants and Animals
80000 - News or discussion
90000 - Related pictures, reports, surveys
100000 - Products and Equipment
View Type Category Hierarchy