ProntoForms’ SharePoint List Repeatable Data Destination changes the game for automating field data collection and processing, making it easier to get structured repeatable data into a SharePoint list.
Prior to the launch of this new feature, citizen developers could only easily create one SharePoint list item (row) per submission. Some of our customers were crafty and built a sophisticated workaround, but this often proved to be time-consuming and created unwanted dependencies and risks.
The solution: SharePoint List Repeatable Data Destination
ProntoForms’ SharePoint List Repeatable Data Destination allows citizen developers to benefit from repeatable sections without any extra configuration. The feature gives field teams easily understandable, in-context data at a glance.
You will now be able to create an item in your SharePoint list for each row in a specified repeat section. To support repeats, we have added the SharePoint list data destination to the list of destinations that support repeats. On the Destination itself, you will be able to choose from two options: Regular Destination or Repeatable Destination. Selecting the second option will allow you to configure the repeat section to loop over the rows in the repeat, without having to specify how many rows there are. The DREL in the Configuration tab will be executed from the context of the repeat row.
A practical example
Perhaps you want to capture records for an Asset Inspection/Survey and store them in a SharePoint list(s). You’ve set up a form to capture what you’ve established to be the most valuable information needed, including the survey date, employee, and auditor. The form also has a repeatable section to be used by the field technician to enter equipment details such as type and condition as rows in a table.
Here are two ways you can send the data to your SharePoint list.
The most straightforward approach to take is to create a single SharePoint list repeatable data destination in ProntoForms and a corresponding list in SharePoint.
This method makes the form submissions data easily readable as it allows you to combine data from a repeat section with top-level answers in the same list.
This second option is ideal for using the form submission data with other systems or processes, such as building an analytics dashboard in Power BI. Taking this route minimizes data duplication.
For this option, you will need to use two SharePoint list data destinations; one regular, one repeatable and two SharePoint lists. The Parent List will capture the top-level survey information using a regular destination, and the Child List will capture the equipment details using the repeatable destination.
The benefits gained from using SharePoint List Repeatable Data Destination
This new feature takes the burden off IT staff and citizen developers by helping your organization bring richer data into SharePoint as your centralized system of record with greater ease.
The time citizen developers save with this new feature is significant. There’s no longer the need for custom work and fancy workarounds. They can configure one repeatable destination and hook it up to multiple parent destinations, rather than having to create hundreds of destinations to account for any possible repeatable section row entries.
Repeatable destinations also minimize update time. Rather than updating each row’s destination, citizen developers simply edit a single destination if a configuration changes on SharePoint and have it reflected across the board.
Now it’s easier than ever to expand your use cases for repeatable sections and collect additional data. In addition, it’s simple to connect this information with analytics tools like Power BI give you the insights you require.
Learn more about SharePoint List Repeatable Data Destination
ProntoForms’ SharePoint List Repeatable Data Destination can be reused across multiple forms to create new or update existing items in SharePoint lists easily. You can also adapt this feature for complex workflows, such as sending data from multiple repeat sections or forms to a single SharePoint list or ensuring necessary business metadata is populated to aid downstream processes such as Power BI to detect relationships.