It's important to understand that PreciseFP has client and prospect accounts. Within that client and prospect account we have a client and a co-client record. And then we have profile data. We do not have the concept of a family member, that is profile data for us. Same as IRA's or 401ks, Insurance, etc., those are simply profile data.

Whenever we are importing or exporting any type of data, any piece of information that is not the household itself or the client or co-client, everything needs to have an ownership. For example, a family member needs to have an ownership. Usually they belong to the household the same way that the client and co-client need to belong to the household. Financial accounts will probably belong to the client or co-client or even to the household, this would just depend on how you organize your information in Salesforce.

In this example below, we can see that this asset of Personal Property has an ownership. It belongs to the account.

You can scroll down to the bottom of any page and click on New Map.

You'll see that you have the ability to select ownership. This field in Salesforce is used to identify the ownership of the record. It will be a drop down of all potential fields that could be an ownership and you need to select one. We cannot inform you which to chose. This is something you will have to discover in your Salesforce structure.

Once an ownership is selected the ownership value field must be selected with Account. This will be the only option available to you. If the ownership field is an actual contact record, then the ownership value would be filled in with the options client, co-client and then all of the ownership dynamic drop downs that we include in our dataset that could potentially could have client or co-client.

The Title, Ownership Field and the Ownership Value are the only mandatory items needed to create a new mapping.

Active On: Select if this map should only be for importing, exporting or both.

Filter: This can only be used on importing.

Here is an example of a map that allows importing that has filtering on it.

We can see the specific filtering here

When we click on the pencil icon of the map to edit, we can see the filters that are done in a different way.

There is also the option to do advanced filtering.

Here is an example of a map that has advanced filtering.

If I click on edit map the advanced editor opens and I can see this query. Instead of just being some fields and some values that I select. If you need to query a related table and you cannot figure out a filter in your main object that is coming in, then you will need to do an advanced query and to do an advance query you will need to understand how to create one.

Note that this is NOT something that PreciseFP can assist with. You will need to contact your Salesforce administrator for assistance in creating a query.

Export Operations: Once you export the following operations will happen right after.

Example of export operations, you can see that there are two steps that happen after the export.

This JSON is used whenever there are extra steps that are needed to relate whatever object record that is being created in Salesforce on export. Whenever you need to relate that to a household or a contact (client or co-client), create extra steps or use extra tables that is when you'll need to use the export operations.

Note that this is NOT something that PreciseFP can assist with. You will need to contact your Salesforce administrator for assistance in creating a JSON structure.

The identification settings is the section that is responsible for all of the relations or to define all of the logic needed for organizing or identifying or relating a household and the client and co-client within that household which in our case they are called accounts and then the client, the co-client or account and contact.

Identification is set up in sections and have similarities to what was explained above for filtering and advanced filtering and export operations.

Object for client/prospect accounts: This is your Salesforce object that you want used for accounts.

Object for client/co-client contacts: This is what object should be used for client/co-client contacts.

In most cases these objects are different except for Financial Services Could where they are the same object for both.

This is where filtering is set up to identify what is a client or prospect. Whenever we import a household from Salesforce, what fields should we look at to insure it's a client or prospect same on export. We also set up an account name.

Clicking on advanced editor will allow you to input an advanced query or an advanced filter. Note that this is NOT something that PreciseFP can assist with. You will need to contact your Salesforce administrator for assistance in creating a query.

This is where you define client and co-clients and also where you define the search. The Client Contact Identification and the Co-Client Contact Identifications is where you define the filtering that will be used to identify which contact and which record is the main client and which one is the co-client. Whenever you are importing an account from Salesforce, one of the first things that we do is search by that account in Salesforce. Sometimes the search is simple and sometimes it requires a query. If a query is needed, note that this is NOT something that PreciseFP can assist with. You will need to contact your Salesforce administrator for assistance in creating a query.

Contact Exports are ONLY needed when you have advanced queries. This again is not an area where we can tell you what to place here. You will need to reach out to your Salesforce admin to get guidance on the JSON structure needed here.

This area is where you're defining which fields in the contact object should be used to store our required fields which are First Name, Last Name, Email Address. Mobile phone is here but it is not required, it can still be defined. These cannot be defined in the mapping but rather here because they are used to create an account whenever you import from Salesforce.