Advanced Mapping with Relationships

Devs -

Referencing an Existing Action from Another Action (Lookup Fields)

FluidReview offers a way to reference an existing action from another action. This occurs in the field mapping of a push or pull action.

To reference an existing action:

  1. Select Configure your site from the left-hand navigation.
  2. Click the name of your Salesforce integration.
  3. Click the Add Action button. This will open a dialogue where you’ll configure the action.
  4. Choose Push to Salesforce or Pull from Salesforce.
  5. Begin setting up the action as you normally would.
  6. In the FluidReview field dropdown, select “Salesforce object from existing action”.
  7. Select the action that you want to map.
  8. Complete setting up the action as you normally would.

The mapping of lookup fields follows a FluidReview object sync with the Salesforce object. Because of this, any lookup fields you plan on syncing to should be optional in Salesforce. If not, the initial sync will fail because we can't provide the lookup field in the original sync.

For more information on Lookup and Master-Detail relationships see:
https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/relationships_among_objects.htm

Note: You can not reference a Master-Detail field or required Lookup field when using the “Salesforce object from existing action” FluidReview field in the field mapping section.

 

Example:

Let’s say you have a submission with a form asking for contact information from an applicant and their former boss. In Salesforce, you want to keep track of the applicant as a “Client” record, and the former boss as a custom “boss” record. You also want the boss record to have a field that points to the applicant, ensuring that there is a link between the two. In this configuration you would need two actions.

Action 1 (Applicant)
Submission owner email -> Client email

Action 2 (Boss)
Form question [what was your former boss’ email?] -> Boss email
Salesforce object from existing action: Action 1 -> Applicant

In this example, when the applicant completes their submission, a client record will be created with the applicant’s email, and a boss record will be completed with the boss’ email (The applicant entered that information when filling out the application form). The boss record will ALSO have a link to the client that was created for the applicant. In this way, when going through your boss records in Salesforce you will be able to see which applicant belongs to which boss.

 

Linking Two or More Salesforce Objects (Junction Objects)

A junction object in Salesforce is an object that links two or more Salesforce objects. It will have a Lookup OR Master-Detail Relationship with references to the two related objects.

We have the ability in FluidReview Salesforce to map Junction objects using lookup fields.
For more information on junction objects see: https://developer.salesforce.com/docs/atlas.en-us.fundamentals.meta/fundamentals/adg_relationships_many_relationship.htm

Note: You can not reference a Master-Detail field or required Lookup field when using the “Salesforce object from existing action” FluidReview field in the field mapping section.

Example:

Like the Lookup Field example, let’s say you want to keep track of an applicant’s former bosses, but instead of one boss, you want 3 bosses. You could use the same technique as above and add the applicant to each boss record. However, there is another way you can link these items together. Instead of having the boss reference the applicant, you can use a custom object to reference the applicant AND all of the bosses. The configuration would look something like this:

Action 1 (Applicant)
Submission owner email -> Client email

Action 2 (Boss 1)
Form question [what was your former boss 1 email?] -> Boss email

Action 3 (Boss 2)
Form question [what was your former boss 2 email?] -> Boss email

Action 4 (Boss 3)
Form question [what was your former boss 3 email?] -> Boss email

Action 5 (ApplicantBossJunction)
Salesforce object from existing action: Action 1 -> Applicant
Salesforce object from existing action: Action 2 -> Boss 1
Salesforce object from existing action: Action 3 -> Boss 2
Salesforce object from existing action: Action 4 -> Boss 3

Now, when the submission syncs to Salesforce, a new ApplicantBossJunction (This is the name I gave my object when creating it in Salesforce) is created, and that record will reference each of the newly created bosses as well as the newly created client.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.