InfoPath Dev

 Hey Guys

 I have started to design a PC setup form that our customer will complete, the form will be emailed to the customer to complete and then emailed back so we can store within our SharePoint 2013 enterprise site

The form has a client drop down that connects to a SharePoint list to show all our clients, when you select a client it will show a section just for the client with specific setup options.

The downside to this is we have over 50 clients so I don't really want to create 50 rules to show a specific section for each client.

I had planned the process working like this, our staff member go to the form library and creates the form by selecting the client from the dropdown and selecting the date, save them form, the form will have a rule setup that makes the client dropdown read-only so the client cannot change this when they receive the form via email, once they client has completed the form they email it back to us and we add it to our Sharepoint to overwrite the original.

I have thought about maybe making the form library email enabled so the client emails it back directly to the library??

Can you suggest a better way to achieve what I am trying to do?

Thanks 

Hi Matt,

If the sections are built within the form, then you would need to create rules for each section to be hidden or shown, which is what we are going to avoid. I don't have an idea of how your form's logic is set up but what I would do in this case is, if you are not displaying the secondary data source onto the canvas, basically setup the main data source's schema onto the canvas and add rules to display the queried value onto the designated main data source field. Add hide/show conditional rules for sections that are blank based on let's say a status.

Generally, what you would want to have is a layout that is very generic and applicable to all clients, and display it smartly so you could add hide/show rules in a minimal way.

I hope this helps.