First Time Using Element Mapper
To get started using Element Mapper, you can use the Element Mapper UI or our platform object definition/transformation APIs. If you are just getting started, we would recommend using the UI to help familiarize yourself with the different pieces that make up Element Mapper and how they work.
Using Element Mapper UI
This guide is here to get you up and running with Element Mapper. We have provided step by step visual directions, as well as, a video of the same instructions taking you through the whole process. Watch the Video or read at your own pace.
This guide reviews the minimum number of steps to get you mapping your data with the leading Cloud Services using Element Mapper. If you have not signed up for Cloud Elements Service or authenticated an Element with us, see the Getting Started Guide.
What you will need:
- Cloud Elements Account
- A Provisioned CRM Element (Salesforce, SugarCRM, ZohoCRM)
Don’t have that set up?
Check out the Getting Started Guide to get set up.
Salesforce will be used for this demonstration
What we’ll do:
- Access transformations.
- Create an account object.
- Map fields to the account object.
- View the object.
- Sign in to your account at Cloud Elements
- Once you are logged in to the Cloud Elements, click My Instances.
- Click Transformations for the elment that you want to use.
Create an account object
- Select an Object. We’ll use the Account Object as the example.
- Click New Object.
- Name the Object, e.g. “myAccounts”.
Note: For some elements, you can see the methods associated with a specific object and the direction represent request and response. To see the methods associated with each object, click Display Methods under the resource name. In the example below, the custom fields Key and Value appear only in the POST
and PATCH
methods, but not GET
.
Map fields to the account object
- Drag and drop some Fields to map to the object “myAccounts”.
- Click the pencil to edit the object fields.
- Name the field – assign custom value e.g. “myName”.
- (Optional) Select Yes or No to “ignore unmapped” fields.
- Yes gives you the flexibility to map only the fields you wish to the object.
- No gives you the option to map the custom fields of your choice and all available fields for the object within the Endpoint (Salesforce in our example).
- OR you may click “Add Field” to map fields manually. This option gives you the power to create nested objects – meaning you can create a myAddress Object and map only the fields you wish to add, e.g. BillingStreet, BillingCity, BillingState.
- Name the Object e.g. “myAddress”.
- Select type e.g. “object”.
- Name Field to Map e.g. “Address”.
- Click the green check mark to complete the action.
- Drag and drop the fields you wish to nest underneath the object.
- Assign values to each of the fields
- Name the Object e.g. “myBillingState”.
- Select type e.g. “string”.
- Select Field to Map e.g. “BillingState”.
- Click the green check mark to complete the action.
- (Optional) Select the Level you wish to map the transformation with.
- Organization = Your Company Level.
- Select “Transformation Level”.
- Instance Level = Only for one Salesforce Connection.
- Organization Level = Your Company Level.
- Account Level = A customer of your Company.
- Click Save.
- Click “X”
View the object
- To view your Object, click Documentation.
- Scroll down towards the bottom of the window to ” GET /{objectName}” and click the link
- Scroll down to Parameters.
- Input the name of the Object you created, e.g. “myAccounts”.
- Click Try It Out.
- View Mapped Objects.
CHECKPOINT
What we did:
- Signed in to Cloud Elements.
- Created an object.
- Mapped fields to the object.
- Viewed the object.
Don’t stop there, keep exploring the other functionality that Element Mapper has to offer by creating more custom objects with different Element Endpoints like HubSpot, QuickBooks and more.
If you have any questions, please contact us at support@cloud-elements.com
We will do our best to get back to you within 24 hours. Your success is our success.
Thanks for reading.
The Cloud Elements Team