InfoPath Dev

I need a form where a user can submits to a list, but can't view the list.  Is this possible?  I'm hoping qRules has some super-duper way to do it!  =)

I have SharePoint 2010 and qRules.

If not, what would be the best way to accomplish this task?

THANKS!

Well - I would think you could do this with a UDCX that uses SSO? So set up your SSO with a user that can submit to the list, and then change your submit connection to a UDCX and modify it to use the SSO. You might want to have a column for the actual user name too that you map, so you know who submitted what.

I think I understand what you are saying, but not quite what to do.  =(

Would I have a forms library with the form?  And then, when the user fills out the form, instead of saving back to the forms library, submit the data to another list using UDCX? 

What would I do if I needed to display the data in the same form format after it was submitted (but read only)?  Would I make a new form to pull the data from the new list?  ARGH!

 Your original question (which is what I was answering) was:

klink:

I need a form where a user can submits to a list, but can't view the list.  Is this possible? 

 

Since you asked about qRules, I assumed you were using SubmitToSharePointList. Why don't you outline what you are trying to achieve and I'll see if I can help you come up with an approach? 

You're right.  I was kind of vague.  Here's the requirements:

1. User needs to fill out a form when they conduct a Fire or other drill. It should be web-enabled.
2. Because the form contains some sensitive information, most users should not be able to see other completed forms.  They actually don't need to see their own again, either, once it is submitted. 
3. Each "Site" needs to do these drills.  There may be several drills per "Site."
4. The Supervisor for a site needs to see drill information for their particular site, but not for other sites. 
5. There are people that should be able to see drill data for all sites.
6. There is a report (form) that can be run either by "Site" or all drills within a certain time period.  This shows MOST information, but not all.  If they want to drill down, they should be able to bring up the form (or maybe this could be a toggled section).

I haven't started creating the form or the report.  I can use qRules if it would be more efficient.

Thanks for your help!

 For item 4, will Supervisors be looking at one drill at a time? Or an aggregate?

Generally, I'd use a couple forms for something like this.

1. Due to your viewing restrictions, I'd probably create a regular (library) form and have it submit data to a SharePoint List, using UDCX for permissions as I initially mentioned. No need to also submit the XML to a library, the library is just for "hosting" the form the user will fill out.
2. A report form would then be used for 4 - 6

I think the tricky part is actually going to be for the reporting because of the permissions based on site. If the list isn't available on the Quick Launch, is your supervisor group capable of finding it? How dire would it be if they were able to view the list? Is simply restricting them to only seeing their own sites using form logic in the report form adequate? If not, you may end up having to submit different sites to different lists in order to handle for these permissions.

 

For #4, ideally I would like to show the aggregate for each type of drill (with a total number of each drill) and then be able to click a + sign and show the detail for each.

Site A

 -  Fire Drill               3

      Fire Drill    1/1/2015    Blah Blah Blah
      Fire Drill    3/1/2015    Blah Blah Blah
      FIre Drill    6/1/2015    Blah Blah Blah

 + Tornado Drill        5

 + Medical Drill         1

______________________________________________________________

Any tutorials for that?  =)

As for restricting the permissions for the site, I think if I do it the way you are suggesting, I can limit what they see by linking to a view with only their site's information.  I'm not too concerned that they will be trying to find a way to get to the list if it isn't readily available to them.

 So - you'd just need to do a report (dashboard) form that queries the list the initial form submits to. You can query for just the site they have access to (or add the other filters you mentioned earlier for people who have access to all sites). Then you can use XPath to aggregate the data. See attached for an XML based sample of what I mean. You'll probably need to use qRules for sorting, since a normal SharePoint List connection isn't going to let you sort by multiple columns and for users who have access to all sites, you need to sort by Site then by type.