I wanted to start off by saying Happy Holidays and Happy New Year from my family to yours! What is better than a little light ProntoForms light reading over the holidays? I am posting this one into General Discussion because I am hoping to hear what a few things that everyone else has learned this year?Here is something that I learned about only recently and really wanted to write about it. I am not going to go into how to create this destination or anything in detail in this post just a few things to think about when working with ProntoForms.
Microsoft Lists act slightly differently than our other data sources because of the way that Microsoft handles the API requests, but it is one of the more powerful out-of-the-box destinations. Here a few “gotchas” that I have learned over time in no particular order.
Now comes the part where things get more fun. Using a Flow, it can watch each new entry check for certain conditions and then do something (anything) else. Try to parse out our standard JSON output and see if you can flatten the data to analyze the data even more.
The combination of ProntoForms (to collect the data), Microsoft Lists (to hold the data), Microsoft Flow (to manipulate the data) and PowerBI (to analyze the data) you can fully automate and control what is happening in your business with all the oversight required to make sure things are running smoothly.
Happy Holidays and a Happy New Year
Microsoft Lists act slightly differently than our other data sources because of the way that Microsoft handles the API requests, but it is one of the more powerful out-of-the-box destinations. Here a few "gotchas" that I have learned over time in no particular order.
Hi LisaI have lots to say on this, it is something we looked at extensively when we were working on updating the SharePoint list destination to be able to support repeatable sections.The short answer is: you need to send your attachment type questions, such as images, to a SharePoint document library instead of a SharePoint list.We have a separate data destination for a document library: Microsoft SharePoint Document Library Data Destination and the good news is that this destination already supports images (& other attachments) from the entire form, regardless of if they are in a regular or a repeatable section.
Know that you can have more than one document library in a SharePoint site: Create a document library in SharePoint this allows you to separate and organize your files as you need.
In the past, ProntoForms did have the ability to send attachments to a SharePoint list, but a few years ago, Microsoft introduced a new API where they no longer gave us the ability to send attachments to a SharePoint list. At the time, we weren't sure if it just wasn't there YET and if it was coming, but that API endpoint never got created. Now I suspect it was intentional so that users would move towards using SharePoint Document Libraries instead, as they are much better suited for files.
We hope to create a recipe explaining how to set something like this up, but please ask if you need any help!
Hi LisaWow, you've got it going all the way back into SharePoint, as what, an embedded chart? That hadn't occurred to me, I didn't know you could do something like that - cool! Why did you choose to do it this way? I could guess it is because it makes it easier for non Power BI users to see only the data you want them to, in an environment they are already familiar with - but I don't want to assume I know you reasons.Now that you are starting to use this, there is an possible enhancement that I will need to ask customers about, to see if it is something they care about.You'll have noticed that when we send data to a SharePoint list, we create a column called 'ProntoForms ID'. This contains the submission ID from our system.We don't create this column when we send files to a SharePoint document library. By default, those files have the submission ID in the filename that is visible in the library, but it isn't separate in its own column.My question is, do you see a need for the ProntoForms ID to be created and populated as a column in the SharePoint document library as well?
Thank you Cesar, that is really useful.
As we were designing how to handle repeatable sections in SharePoint, we had looked into using SharePoint lookup columns to create relationships like this. However, when we polled some of our customers, none of them were really using lookup columns and implementing support for them was a fair amount of work - so we didn't see the need to spend development effort on it.I'm happy to learn about this option to do it in a different, but still automated, way.Do you have any ideas on how to do something similar but in a 1 to many relationship? In the image I shared above, the document library has multiple images all linked to one form - it would be great if I could have a link in my main list that would open up a list of the attachments that came from that form.
"txtContent": "Name for HyperLink",
"href": "='https://sharepoint.com/sites/sitename/firstFolderName/' + [$name of the sharepoint list column matching the n ame of the folder containing the pictures using _x0020_ to substitute spaces in case you have them]"
"txtContent": "Name for HyperLink",
"href": "='https://sharepoint.com/sites/sitename/firstFolderName/' + [$