In order for your new Office in RAMCO to get created in M1, here are a few tips to ensure the Office data is prepared optimally, and some tricks to try if you encounter an error.
Make sure all required fields are filled out
M1 has some fields that are required, but that are not required in RAMCO, meaning they can be easily missed. While you may be able to save the new Office in RAMCO without these fields, the Office won't be transmitted to M1.
You can access the M1 Manual page with the list of these fields here: https://nationalasnofrealtors.mcoutput.com/1374755/Content/M1%20User%20Manual/Office%20Record%20Fields.htm?Highlight=required%20fields
Here's a shortlist of the required fields, with the ones most commonly missed highlighted in bold:
| M1 Field Name | RAMCO Field Name |
|---|---|
| Office ID | NRDS/M1 ID |
| Primary Local Association ID | Association (on Office Membership record) |
| Office Status Code | Status (automatically set as Active when you create the Account record) |
| Office Contact DR | Primary Contact |
| Primary State Association ID | State Association (on Office Membership record) |
| Office Contact Manager ID | Office Contact (if left blank, will be filled from Primary Contact) |
| Office Business Name | Account Name |
| Non Member Salesperson Count | No. of Employees |
| Street Address | Street Address: Street 1 |
| Street City | Street Address: City |
| Street State | Street Address: State/Province |
| Street Zip | Street Address: ZIP/Postal Code |
| Office Phone Number | Phone (separate field from the Primary Contact's Mobile Phone) |
In addition to these fields, you'll need to make sure the Office has:
- An Active Primary Contact with an Active Membership (this person should display in the Membership and Contact Records sub-grid)
- An Active Primary Office Membership (this should display in the Office Memberships sub-grid)
Creating a new Office via the Membership Application wizard is our usual recommendation, as it will walk you through getting all of this information in in one go. However, there are two scenarios where you'll need to take a slightly different approach.
-
You are creating a new Office for an existing Member, and thus a Membership Application is not appropriate.
Manually create the Office record, ensuring you meet all the requirements above. You can save the Office record and add the information as you go, as long as there is no M1 ID set.
Once you have all of your information, go to the Office Membership and run the "Generate NRDS ID" workflow. This will add an M1/NRDS ID to the Office, which will send the message to M1 to create the Office there.
-
You are processing a Membership Application for a new Member, who will be the DR of the new Office (aka: the Chicken & Egg scenario).
We have a separate article on how to deal with this scenario: The Infamous Chicken & Egg Scenario
Resolving M1 sync errors
You've gone through all the steps to add your new Office, pushed it up to M1, and...it didn't work. What now? Of course, you can always reach out to RAMCO Support and we'll be happy to troubleshoot, but here are a few tricks to help you potentially resolve it on your own in a pinch.
-
Review the requirements.
This is the "turn it off and turn it back on again" advice, but we always want to start with the low-hanging fruit and work our way up. If the required fields are all filled out, and the Office has an Active Membership and Active Primary Contact, then we can dig deeper.
-
Check the Mailing Address.
Although Mailing Address is not required to create the Office in M1, it's often filled out in RAMCO, and many times using the "Same As: Street Address" option. On occasion, we've seen that this causes an issue passing the data to M1.
Check if the Mailing Address is set to "Same As: Street Address"; if so, change it to Enter Address instead, then follow the M1 ID reset process below to try pushing the Office up to M1 again. Once it gets created in M1, you can change the Mailing Address back.
-
Trigger another Create message.
When the M1/NRDS ID is generated for an Office, that is what triggers the creation of the Office in M1. We can cause this Create event again by removing the M1 ID from the Account record. The field in the Account Information section should be unlocked for editing:
Copy the ID so you have a backup. Then remove the ID from this field, save the record, add it back, and save again. Reentering the M1 ID in this way triggers the Create event again, so any changes you may have made to the Account record since first generating the ID will now be included in the transmission, which often resolves the issue.
If you try these steps and are still unable to get the Office to go through, please reach out to RAMCO Support and we'll be happy to help.