InfoPath Dev

I'm using the contact selector for the first time. I have the template part installed on my form and working properly. When my users submit the form to a form library, I want to use a Sharepoint workflow to grab the names in the contact selector and email them. Since it's a repeating field, how would I get the individual names to email them?

 Know what I mean?

 Thanks!

 selch

 And while were talking about this web part, it seems to perform fine in InfoPath but in the browser, the selected names do not appear in the list on the right unless I search for additional people. When I add those additional people the previous person shows but that new person doesn't... until I search again, etc.

Hi, and thanks for trying this new webpart. We are investigating these issues you've reported and we'll reply soon.

Hi selch,

Please try the following:

To get the names:

1. Open your XSN in InfoPath Design mode.
2. Go to Tools > Default Values.
3. Expand 'UserList' and check the box for ‘Alias’ then click OK.
4. In your canvas, double-click on the ‘Alias’ repeating table (the table on the right), go to the ‘Display’ tab and click ‘Conditional Formatting’.
5. Add a condition that hides the control if ‘Alias’ is blank.
6. Double-click on the x button, go to the ‘Display’ tab > ‘Conditional Formatting’ and delete the only condition you find there.
7. To concatenate the list of selected users separated by semicolons, you can use the ‘eval’ function of InfoPath. For example, this formula: eval(eval(Alias, 'concat(@my:name, substring(";", 1, string-length(@my:name)), " ")'), "..") will return UserA; UserB; UserC; and so on. Make sure that Alias points to the corresponding node in your Main data source.

IPFS issues with selected names not showing until another search:

As mentioned in the qRules User Guide ‘Use qRules in IPFS’ section, you would need to make sure that all the controls that make use of the qRules commands including buttons that execute them (if present) are set to ALWAYS send data to the server.

1. In Design mode, double-click on the arrow (button) to open its properties.
2. Go to the ‘Browser forms’ tab and select ‘Always’.

Those should hopefully resolve your issues. Please post back otherwise. Thanks for your interest in using Qdabra’s products! :)

Cheers!

 Thanks Mel both those things work and I greatly appreciate it. One more question on the method to get the names. What you described above gives me back the user's display names however, I'm trying to email them from a sharepoint workflow and it won't take just semi-colon separated names. It's looking for either domain\user or user@domain.com formats. Is there a way I can cull that from Contact Picker?

Much thanks!

 You guys are awesome.

Selch - glad those worked for you. You can obtain the users' email addresses by adding a data connection to the Qdabra Active Directory Web Service, GetUserInfo method.

1. In Tools > Data Connections, add a receive data connection to a web service.
2. Enter your AD web service URL and select the GetUserInfo method.
3. Leave the username parameter blank and disable ‘automatic retrieve’ on form open.
4. In your main data source, Alias field, add another attribute such as ‘email’. It’s XPath should be something like: /my:myFields/my:UserList/my:Alias/@my:email
5. Modify your >> button ‘Insert User’ rule by adding the following at the bottom of your Actions list:
   a. Set the value of the GetUserInfo username parameter (/dfs:myFields/dfs:queryFields/tns:GetUserInfo/tns:username) to the resulting FindUsersByName value node (/dfs:myFields/dfs:dataFields/tns:FindUsersByNameResponse/tns:FindUsersByNameResult/tns:entry/@value).
   b. Query using the ‘GetUserInfo’ data connection.
   c. Set the value of the qRules Command node to: concat("SetValue /xpath=/my:myFields/my:UserList/my:Alias[last()]/@my:email /value=", Value[Key = "mail"]); where Value[Key = "mail"] is your resulting GetUserInfo Value node, filtered such that Key is equal to mail.
6. Lastly, in your 'eval' formula, change @my:name to @my:email. Your formula should be something like: eval(eval(Alias, 'concat(@my:email, substring(";", 1, string-length(@my:email)), " ")'), "..")

Hope that helps!

Wow. That hurt my brain a bit but I got it! Thank you SO much!

You're most welcome! I'm so glad you've got it all working! :)

Cheers!

 Mel and all, related to this thread, can you help with with a rule that would remove all users that were selected using the Contact Selector in one fell swoop? I'm hiding and showing the section that contains the Contact Selector. If they choose to hide it I'd like to make sure it also removes any users they may have added using the selector. 

 Thanks much!

Hi, selch - a rule that sets the 'Alias' repeating field of the UserList group to blank (i.e. no value) when your users choose to hide the ContactSelector section should do the trick. Hope that works. Let us know otherwise. :)

Perfect, thanks!

I was setting the Alias' Name attribute field to blank and that only sort of worked. :)

Sorry Mel, one last thing.

As per previous posts in this thread, I'm using the contact selector to grab a list of email addresses. I'm using the eval statement you gave me - eval(eval(Alias, 'concat(@my:email, substring(";", 1, string-length(@my:email)), " ")'), "..") to do this. Now, when my user chooses to hide the Contact Selector I'm setting the Alias field to Nil to clear out any selections they've made. I'm also setting the field that's using the eval function to Nil to clear out the gathered email addresses. That works fine.

However, let's say the user changes their mind and they show the Contact Selector again and decide to select some people to email. The Contact Selector appears and no users are select as we'd expect. (Because we cleared the Alias field.) Great. BUT, when they select a new person with the Contact Selector the field that contains the eval function populates with any previously selected user's email addresses and the newly selected person's email address - even though we've set that eval field to Nil when we hid the Contact Selector before. Almost like it's caching the email addresses

Make sense? Ideas?

Hi selch, sorry - you will have to clear the name and the email attributes as well, i.e. not only the Alias field. So in your rule, add the actions to set those attributes to blank.

Hope that works! :)

Can you please give some assistance with the contact selector?  What I need to do, is clear out the details previously selected when the user clicks on a specific checkbox.  I really would like to do this via rules and not code.

When the user checks the "Clear all details" checkbox, I would like to clear all of the other fields.  I have everything working well except for the contact selector field.

Is this possible?

Hi, kerriejones -

If you're using Qdabra's Contact Selector XTP, then I'd assume you have qRules injected in your template, correct? If so, I believe you can use the qRules Delete command to select your Contact Selector repeating group. The command syntax will be something like: Delete /xpath=/my:myFields/my:group/my:repeatinggroup.

Hope that helps!