InfoPath Dev

Try this (no code): InfoPath - User Roles in Browser-Enabled Forms Using AD Groups It doesn't use SharePoint Groups but can use AD groups (Security Groups and/or Distribution Lists).  Since you're willing to use code (requires administrative approval for browser forms), then you might be able to leverage the built-in ...

I think this has to do with your profile database.  The people picker doesn't really connect to AD but rather to the profile database.  The profile database gets populated with information from Active Directory, but if that profile database gets wiped or doesn't get updated, then you may have incomplete information in that ...

Just remember that you need to use Encoded Absolute URL for the reason I gave instead of Server Relative. Also, unless you want that whole URL in the body of the email, I suggest adding HTML like this: <a href="http://full-URL-here">[%FormLibrary:FormName%]</a> This way, your users see the name/title of the ...

You create it dynamically using the Build Dynamic String action in SPD.  In the BDS, you need to concatenate static URL text with one piece of metadata from your form.  I keep writing this up, so I need to just do a quick blog on it so that I can link to it from now on.  Here is how it will ...

Don't know how I missed your question, sorry.  Can you explain how a form-level rule made your repeating SP date node display as a date? I would have originally answered for you to try and change the control to a date box instead of trying to format the data type.

I thought I may have a comment on my blog from you about this, but I didn't!  =P  It works exactly like GetCommonManager and GetUserProfileByName in terms of the parameter it expects.  The returned data set is much different, but I've never done it and gotten 0 results.  I would ensure that the profile import is fresh ...

I use this method in addition to the GetUserProfileByName, and I find that it works exactly the same way.  It accepts the same parameter - userName() - and returns a subset of the same type of data, but it returns that data for the user's manager, which is cool.  Are you passing the correct parameter?

Check your syntax on the Contact Selector fields - they have to be exact.

You have to make the gpContactSelector group in your main data source, which is what you drag to the canvas.  You don't drag the control, but rather the gpContactSelector group and then you choose the Contact Selector control when prompted..  If your form was built initially on the database schema, then the main data source is ...

Something is just off - can't tell without seeing the XSN and the exact data.  The syntax of the CustomerID has to be exact for the filter to work. Make sure on the "set a field's value" that you're first choosing the destination field and THEN for value choose the sharepoint list secondary data connection node for ...