Best Practices

Don't tell @Pat Cooney but I was a little late in getting this post out, for good reasons though. I was fortunate enough to get to travel down to San Diego for Field Service Medical and had the opportunity to speak to some of you. A reoccuring theme in my talks at the conference was having the ability to update many different Salesforce objects in one form submission. Salesforce Repeat destinations can help us immensely in this process, being able to use information from a repeat section to create or update many different objects.

Gone are the days of creating WAY TOO many destinations to account for the repeat section in your form. Gone are the days when you need to limit the number of rows that can be added into your repeat because you knew each row would mean more destinations. Salesforce Repeat Destinations to the rescue.

In my example today, I have a few different Parts Orders that I need to update the tracking information of (as with all my examples, replace "Parts Order" with "Work Detail" or "Any Salesforce Object") If its an object in Salesforce, we can update it.

THE DATA SOURCES:

I am just using a simple Salesforce report as my data source with all the columns that I want to include in my form.

THE FORM:

I have a single dropdown question which will be looking for the WO# and a repeat section that will contain each of my Parts Orders that are on that work order. You can see from the data above that I have 2 work orders each of them containing 2 parts orders.

Using the salesforce report as a data source for the dropdown, we can push all the Parts Orders into the repeat (Ideally, this question would be answered automatically with an app-to-app call from SF or SVMX so your tech doesn't need to worry about it)

I need the tracking information updated so I have added that question to the repeat section as required:

That is all that I am going to configure in my form, but any number of questions can be added to the repeat so that you can update all the required fields in the object.

THE DESTINATION:

With a Salesforce Repeat destination, there are 3 main things that you will need to know to set it up. The Unique ID of the repeat section, the Question Label for the fields you want to update and the question label of the Unique Identifier from a Salesforce perspective (the work order number and  the parts order number)

Prerequisite: An established connection to Salesforce.

On the Salesforce Object Fields of your Salesforce destination, the first field is the API name that Salesforce uses to identify the type of object that you need to create or update.

The fields below are the fields inside the object that you would like to update using answers out of the form. If you are unsure about the API Name of the field in Salesforce, you can use the "Describe Salesforce Object" button to show you a list of all available fields that exist in the object that you specify.

So for my example, I am updating the tracking number in the RMA Shipment Object in ServiceMax as shown below. This is just 1 example, replace RMA Shipment Order with Contact or the WorkOrder object and you can update multiple of those objects. The possibilities are endless! (maybe exaggerated a little there)

On the Update Query tab in the destination, this is where you would specify the conditions as to when something is updated. This would generally be pointing to a unique identifier on the source system, in my case I am using the Shipping Order name which holds the number.

I am using the Part Order Number that is being populated in the form to know what we need to update. If the Parts Order does not exist (which should not be possible at all since we are pulling the data from Salesforce) then it will not use the data on that row.

The result of the set up above is when the tech pulls in the parts orders into the form, adds in the tracking information for each of the parts orders in the repeat section, each of the parts orders will be updated with the tracking information

Have you tried out the new Salesforce Repeat destinations in your forms? What kind of objects are you updating?

Hello

I have seen this post and and I had a question about it.
Why is the option "Response Configuration" tab disabled for Salesforce repeatable destinations?
This feature is esencial to work with salesforce.


Imagine:
A Case can have 1 or multiple Work Orders.
A Work Order can have 1 or multiple Work Lines.
Depending on the line/s added (and here is my repeatable section now), further things need to happen.
For instance, if you add from Prontoforms a parts line using items from inventory, you need to add a second/dependent record to store allocated quantity of the part in the inventory.
Without the option "store all response outputs for use in later destinations" that is impossible. Or is there another way to do it?

Thanks a lot

Don't tell @Pat Cooney but I was a little late in getting this post out, for good reasons though. I was fortunate enough to get to travel down to San Diego for Field Service Medical and had the opportunity to speak to some of you. A reoccuring theme in my talks at the conference was having the ability to update many different Salesforce objects in one form submission. Salesforce Repeat destinations can help us immensely in this process, being able to use information from a repeat section to create or update many different objects.

Gone are the days of creating WAY TOO many destinations to account for the repeat section in your form. Gone are the days when you need to limit the number of rows that can be added into your repeat because you knew each row would mean more destinations. Salesforce Repeat Destinations to the rescue.

In my example today, I have a few different Parts Orders that I need to update the tracking information of (as with all my examples, replace "Parts Order" with "Work Detail" or "Any Salesforce Object") If its an object in Salesforce, we can update it.

THE DATA SOURCES:

I am just using a simple Salesforce report as my data source with all the columns that I want to include in my form.

THE FORM:

I have a single dropdown question which will be looking for the WO# and a repeat section that will contain each of my Parts Orders that are on that work order. You can see from the data above that I have 2 work orders each of them containing 2 parts orders.

Using the salesforce report as a data source for the dropdown, we can push all the Parts Orders into the repeat (Ideally, this question would be answered automatically with an app-to-app call from SF or SVMX so your tech doesn't need to worry about it)

I need the tracking information updated so I have added that question to the repeat section as required:

That is all that I am going to configure in my form, but any number of questions can be added to the repeat so that you can update all the required fields in the object.

THE DESTINATION:

With a Salesforce Repeat destination, there are 3 main things that you will need to know to set it up. The Unique ID of the repeat section, the Question Label for the fields you want to update and the question label of the Unique Identifier from a Salesforce perspective (the work order number and  the parts order number)

Prerequisite: An established connection to Salesforce.

On the Salesforce Object Fields of your Salesforce destination, the first field is the API name that Salesforce uses to identify the type of object that you need to create or update.

The fields below are the fields inside the object that you would like to update using answers out of the form. If you are unsure about the API Name of the field in Salesforce, you can use the "Describe Salesforce Object" button to show you a list of all available fields that exist in the object that you specify.

So for my example, I am updating the tracking number in the RMA Shipment Object in ServiceMax as shown below. This is just 1 example, replace RMA Shipment Order with Contact or the WorkOrder object and you can update multiple of those objects. The possibilities are endless! (maybe exaggerated a little there)

On the Update Query tab in the destination, this is where you would specify the conditions as to when something is updated. This would generally be pointing to a unique identifier on the source system, in my case I am using the Shipping Order name which holds the number.

I am using the Part Order Number that is being populated in the form to know what we need to update. If the Parts Order does not exist (which should not be possible at all since we are pulling the data from Salesforce) then it will not use the data on that row.

The result of the set up above is when the tech pulls in the parts orders into the form, adds in the tracking information for each of the parts orders in the repeat section, each of the parts orders will be updated with the tracking information

Have you tried out the new Salesforce Repeat destinations in your forms? What kind of objects are you updating?