Steven. That is some strange behavior. I would try creating a new template from scratch and see if you can get the spouse field to map properly. It is possible your template has issues. If the condition persists, you may want to open a case with Microsoft.

The advantages of the CRM data model outlined in the post are: 1. Automatic creation of views and tables when creating a new entity. 2. The entity view joins the two underlying tables and retrieves the names of the foreign key id objects into the view so you don't have to create as many joins when querying. 3. The entity filtered view enforces user security so reports built using these views will not show records they should not see.