I have what I would assume is not a uncommon scenario for a client. I have hit a roadblock and it is a deal breaker for the client in terms of deciding if SharePoint is the right product.
They will be providing a service to their clients through SharePoint, something similar to a tenant'd SharePoint environment for hosting. so a client would get the following structure in their site:
The obvious choice is to configure a site template and they use that when creating a new client site. The problem comes in for the Forms for the different libraries and lists.
The want to update and deploy once, and this pushes the updated InfoPath template to all existing sites, which is simple enough: Content Type Form. The issue comes in where a library like "Timesheet" will pull the list items from Employee. So the Timesheet InfoPath form template must effectively use relative URL's to connect to the employee list to pull data, yet InfoPath only allows full url's to lists for data connections, effectively had coding that form to that list.
Is there any way to force the InfoPath form to assume the list exists in the same location as the library it is saving to and avoid using hardcoded list addresses in the template?
I have looked at UDX files but the problem is that the form template will look at one location for a UDX file, and therefore look at one list for source data. So I can't create a UDX file for each site so to speak without some work. a UDX may work for the root site collection, but my client has groups as clients so there may potentially be the following structure for a client:
- Company A
- Company B
Only when capturing time sheets for company A, they must only see employees stored in the employee list for company A, and the same for Company B.