Controls

Re: Another contact selector control with share point issues

warrtalon — Wed, 01 Jul 2009 20:38:06 GMT

I'm not sure you can do that, because the contact selector requires the activex control to be activated and requires the Context.XML file to be added to the resource files. You may be able to use the template part and then go add the context file, but I'm not sure.

As for your original problem, if that username resolves in Outlook but is not working in the email generated by your form/workflow even though the name is resolved in the contact selector, then it again points me to that errant pipe in your example. I'm not sure why you think that's not a problem when it shouldn't be showing up and could easily be associated with the domain name due to being adjacent. Am I just seeing things?

Re: Another contact selector control with share point issues

dvnandover — Tue, 30 Jun 2009 15:05:51 GMT

when i put that username into outlook, It resolved into a user's email address correctly. that is odd.

One side question: Since i am using this contact selector control more than one time so I would like to create a template part for it but i it disable and won't allow me to put in into my template part. Is it doable? In the design tasks panel it said: "Some control have been hiddent based on the current compability settings".

Re: Another contact selector control with share point issues

warrtalon — Tue, 30 Jun 2009 02:19:20 GMT

So if you open a new Outlook message and put in that sag47 domain name, it won't resolve to a user's email address? If you are having issues where the detected AccountIds are not resolving in Exchange, then that points to an Exchange/AD issue.

Re: Another contact selector control with share point issues

dvnandover — Tue, 30 Jun 2009 01:25:22 GMT

i don't think extra pipe is the problem. Some AccountIds worked and some other did not. I tried MyCompay\sag47 by itself and it did not worked neither.

Re: Another contact selector control with share point issues

warrtalon — Mon, 29 Jun 2009 23:35:39 GMT

It looks like an extra pipe (|) is being resolved as part of the first AccountID as opposed to being a semicolon.

Re: Another contact selector control with share point issues

dvnandover — Mon, 29 Jun 2009 20:20:42 GMT

Finally i got it to work with a button but the only problem i saw was that the some of the AcountId were not resolved to the approriate email.
Here is the list of accountId (which is correct)
MyCompay\dn978|MyCompay\mbs42|MyCompay\sag47|

Here is the list of email:
MyCompay\sag47|;DVNGUYEN@MyCompay.ORG;MSTOUT@MyCompay.ORG

As you can see, the last AccountId was not resolved and the warning/error was:

Can someone has any suggestion or direction for me to trouble shoot the issue?

Re: Another contact selector control with share point issues

warrtalon — Fri, 26 Jun 2009 17:46:39 GMT

Attach the XSN.

Re: Another contact selector control with share point issues

dvnandover — Fri, 26 Jun 2009 16:38:06 GMT

I tried to move all 3 rules into my submit button but i can' seem to be able to get pass this expression:xdMath:Eval(xdMath:Eval(../my:gpContactSelector/my:Person, 'concat(my:AccountId, "|")'), "..").

The error said: msxml5.dll
Reference to undeclared namespace prefix: 'my'.
Error occurred during a call to property or method 'Eval'

Has anyone done that before? moved all 3 rules into a button control?

Re: Another contact selector control with share point issues

warrtalon — Thu, 25 Jun 2009 22:19:10 GMT

You're in luck - this can be done, and I have proved it in my own forms. Credit to our own Alec Pojidaev from this forum for the codeless solution. Btw, you should not need any sort of web service for sending email notifications unless it's something really spiffy.

http://alecpojidaev.wordpress.com/2008/12/16/infopath-codeless-programming-walkthrough/

Do the whole double eval trick with the Contact Selector.

Re: Another contact selector control with share point issues

dvnandover — Thu, 25 Jun 2009 20:20:20 GMT

After looking at outlook, i agreed with you now warrtalon. Here is one more question, how do i extract the list of email addresses from the contact selector control? i would like to have it done using rules instead since i did not use any codes from the begining. I have a custom send notification web service and i need to feed the list of email address from the contact selector control after the user has already made their users selection.

Re: Another contact selector control with share point issues

warrtalon — Thu, 25 Jun 2009 17:02:42 GMT

Actually, username is the way i always reference people and always teach clients to do that. It's the only unique identifier. Trying to use first and last names is very hit and miss. Anyway, why not just click the button to look up the user? Isn't that what people do in Outlook - go to the Address Book and find people via last name that way and choose from the list?

I didn't realize you were only testing in Preview - I should have told you that.

Re: Another contact selector control with share point issues

dvnandover — Thu, 25 Jun 2009 16:03:02 GMT

The selector control worked when i created a .xsn file and hosted it in sharepoint server. For some unknown reasons testing it using the preview button won't work. The Check Names button did not work very well when trying to resolve someone's name using FirstName, LastName or LastName, FirstName. I got an Unknown error when trying to do that. This post http://www.infopathdev.com/forums/t/12090.aspx discussed about it and mentioned a software patch for it. This button only worked well when using username which is not the good way in my oppion since it is not a common way for people to recognize one another within any company unless you know and worked with that person. You don't just as people for his or her username when you met the person.

Re: Another contact selector control with share point issues

warrtalon — Thu, 25 Jun 2009 15:39:41 GMT

I hadn't seen that restriction and am not sure it's true, but I can try to test it with an Office 2003 user (if we have any left) or from a server with Office on it (better choice).

Re: Another contact selector control with share point issues

dvnandover — Thu, 25 Jun 2009 14:50:25 GMT

I have checked and checked and checked and found nothing wrong with with any of the spelling issue. I think i am about to give up.

One side note: according to a gentleman name scott in order to use contact selector the users have to have office/infopath 2007 installed on their machines. if that is true then i can't use it since only a few selected computer have infopath 2007 installed right now. Reference to the link above:

# re: Using the Contact Selector Control

Thursday, April 26, 2007 8:13 AM by Scott Heim

Hi Scott,

This is not a supported scenario - the Contact Selector control requires some 2007 files hence your users will need to have Office/InfoPath 2007 installed on their machines.

Scott

Re: Another contact selector control with share point issues

warrtalon — Wed, 24 Jun 2009 18:58:54 GMT

Well, is AD the standard for user information and permissions assignment across the organization? AD would only NOT be what MOSS uses if your organization doesn't use AD as its normal user repository. It's unlikely that your error is due to this. If you're not on the SharePoint team, then you can't really check.

I think you mainly need to focus on troubleshooting your errors that we have not seen yet...or attach the XSN to make it simple.