Forum Discussion
Published InfoPath Form Not Appearing in SharePoint
- luvsqlMay 03, 2018Iron Contributor
I'm on my way creating a new form and will try and learn Flow. Might as well figure this out before adding anymore InfoPath ones. I've created one, saved it to my new list, published it, added my list to my site but there's still nothing in it. Site Contents shows 0 items in my list. So frustrating when thigns publish but go no where.
I went back into the list then Custom Forms and it's still there, shows published, but not on my list contents. Should things not published show up where I publish them to?
- Dean_GrossMay 03, 2018Silver Contributor
You will use Flow to send the data entered in the PowerApp Form to other people.
Here is a tutorial that should help https://collab365.community/user-registration-form-using-powerapps-flow/.
One of the big benefits of Flow is that you can use it send the same data to many places, i.e. it can send an email, post to Twitter and put the data into a SQL database. It is very powerful.
A SharePoint list stores the data, PowerApps makes the data entry form smarter, and Flow sends the data and/or notifies people that the data is ready for them to do something.
- luvsqlMay 03, 2018Iron ContributorDoes PowerApps support the ability to email the contents of a "form" to someone of is this more of a collection of data that we have to then notify someone? We need the contents of the form to be emailed to different people as this data is used to create data in non-Microsoft applications. I'm going to see if PowerApps is usable for fillable forms.
- Doug AllenMay 03, 2018Iron Contributor
Mercedes, don't worry about it. I didn't mention it because you said the submitted forms were being emailed only and not staying the library. If that was the case, you can promote field data from the form into columns of metadata in the library via Promoted fields. Then you can leverage data in approval workflows or some other business process. That is done via the publish wizard (near the end). Again, in your case, you don't need to use it since you're library is purely there host web form templates, not any submitted forms. If that changes, then yes I agree with Dean structuring the submitted forms would likely change.
To your earlier question, the reason they are XML is just how InfoPath forms work. A rendered form is comprised of 2 parts, the data itself (the XML) and the form template (the fields schema holding the data).