WEBVTT

1
00:00:00.200 --> 00:00:03.675
Field mapping tells a connector where each answer belongs.

2
00:00:03.855 --> 00:00:10.165
Start small: one form, one CRM object, and only the information the workflow needs.

3
00:00:10.345 --> 00:00:16.447
A volunteer form might send a person's first
name, last name, and email to a contact record.

4
00:00:16.907 --> 00:00:21.973
After the connection has passed its checks, open Mappings and logs for that connection.

5
00:00:22.153 --> 00:00:25.779
Choose the source form and a supported destination object.

6
00:00:25.959 --> 00:00:32.353
A contact, company, and deal are different objects,
even when several of their fields have similar names.

7
00:00:32.813 --> 00:00:36.352
Use the field definitions returned by the CRM.

8
00:00:36.532 --> 00:00:40.563
Check the internal field name, data type, and required status.

9
00:00:40.743 --> 00:00:44.433
A familiar label does not guarantee a compatible field.

10
00:00:44.613 --> 00:00:49.903
Two fields called Status may accept different values or belong to different objects.

11
00:00:50.363 --> 00:00:52.521
Here is a simple planning example.

12
00:00:52.701 --> 00:00:58.920
First name maps to the contact's first name, last
name to last name, and email address to email.

13
00:00:59.100 --> 00:01:01.074
These are illustrative labels.

14
00:01:01.254 --> 00:01:05.638
Confirm the actual property names in your connector before saving a mapping.

15
00:01:06.098 --> 00:01:07.881
Review more than the field names.

16
00:01:08.061 --> 00:01:11.996
Dropdown values must match values the CRM accepts.

17
00:01:12.176 --> 00:01:15.462
Dates and numbers must use a compatible format.

18
00:01:15.642 --> 00:01:23.310
Decide what a blank answer should do, and check the connector's
behavior before allowing it to clear an existing CRM value.

19
00:01:23.770 --> 00:01:26.535
Choose the supported record action deliberately.

20
00:01:26.715 --> 00:01:28.264
Create adds a record.

21
00:01:28.444 --> 00:01:30.645
Update changes an existing record.

22
00:01:30.825 --> 00:01:34.047
Upsert combines matching with an update or a create.

23
00:01:34.227 --> 00:01:40.638
Define the matching key separately from the field mapping,
and review any suggested mapping before accepting it.

24
00:01:41.098 --> 00:01:46.921
Validate the mapping, then test delivery with one
fictional submission in your test environment.

25
00:01:47.101 --> 00:01:52.243
Validation checks configuration; it is not evidence that a record was written.

26
00:01:52.423 --> 00:01:59.613
Inspect the destination record, including required fields,
blank handling, and any returned record identifier.

27
00:02:00.073 --> 00:02:05.960
Your next step is to review the mapping field by
field and confirm the intended record action.

28
00:02:06.140 --> 00:02:08.872
Keep a short mapping table with the written guide.

29
00:02:09.052 --> 00:02:14.716
Continue with Create, Update and Upsert to
understand matching and duplicate prevention.