-
[quote user="buck_murdock"]Can i base the availablity of this option to a security group, or a list or something?[/quote]
Yes, you can do both, and I have written a separate a blog entry for each. What I can't do is restrict by SharePoint group, but I show how to leverage AD security groups and/or Contact Lists. ...
-
There isn't anything that InfoPath has. You might be able to get Qdabra to make something for you that leverages their Active Directory Web Service.
-
You can show/hide fields in many ways. You can do it all in one view with conditional formatting, or you can do it in multiple views with conditional formatting or omission. You can auto-send people to certain views based on identity and can restrict/show controls based on identity. Review my blog posts that talk about ...
-
Might depend on how you set it up, but you haven't mentioned those details, so it's hard to know. Did you develop your solution similar to what I showed in my blog on this topic?
InfoPath – Auto-Numbering Forms
-
gpContactSelector should not be a repeating group. It is a table, and Person is the row. Only rows repeat, not the table itself. The group2 is repeating, so the things within it will repeat.
-
Is there any way to do what?
-
That's because it goes into SharePoint as a text string, not a repeating data source. In SharePoint, the repeating data source is the list/library itself, and each record is a repeating entry of that group. SharePoint does not have repeating fields within repeating records. This is a known limitation and is not a bug, nor are ...
-
There are many causes for this error:
Is your web application set to allow anonymous access in IIS?
Do your users have the Personal Features permissions given to them in SSP Admin?
-
No, because it's not an actual file that gets opened locally - it's all an ASP.NET page.
-
Do all users have the version of InfoPath you used to create the form template (XSN)?