General

Re: Promote field to Sharepoint as a People and Groups datatype

Carolyn2 — Fri, 19 Aug 2011 02:35:34 GMT

I saw that "eval eval concat" concept before in the thread, but I'm not sure what fields are to be included in the formula. Can you clarify what I should be including? I'd love to be using a database, trust me. :-) Carolyn

Re: Promote field to Sharepoint as a People and Groups datatype

Patrick Halstead — Fri, 19 Aug 2011 01:24:44 GMT

If the number of items is <10 or so you can probably just create separate fields for each and promote them. A bit of a hack, but easy to do.

For larger lists you should be able to concatenate the values together and set them in another field using the eval-eval technique. Then, promote that new field to your SharePoint site. The values will be merged together and you may want to add a delimiter when you do the eval-eval concat.

Another option is to map them to a SharePoint list. You can use qRules plugin to do that or write your own code.

Longterm, you'll want to look at moving your XML data into a database which is ideally suited for downstream processes.

Re: Promote field to Sharepoint as a People and Groups datatype

Carolyn2 — Thu, 18 Aug 2011 23:12:14 GMT

Is it possible to get all the values entered in the repeating table into SharePoint? It doesn't matter to me if they're merged together somehow, as long as the format is consistent. Another developer wants to use this value for a process.

Thanks,

Carolyn

Jaws01:
Yes I do have the People field to allow "Multiple Selections". I have the AccountIDs mapped to a single line of text. "john.doe \n\r mary.smith" (i.e. they appear on separate lines).
In the Workflow when I attempt to update the People group field I get a warning that => the lookup is not guaranteed to return a single valie, if more than one valie is returned only the first value will be be used, do you want to continue ? I said "Yes".

Re: Promote field to Sharepoint as a People and Groups datatype

Jaws01 — Thu, 02 Sep 2010 19:00:21 GMT

Got this to work. Thanks to Mr. Clayton. Here's what I did.

1.) Created a contact selector called it: RR_Members, created another text control and set it's default to be this xpath expression => xdMath:Eval(xdMath:Eval(../my:RR_Members/my:Person, 'concat(my:AccountId, ";")'), "..")

2.) Finally promote the text control to a Text column in SP. Have the workflow, set the People field to the value of the Text column and it works well.

Assumptions:- Create a group called "Person" and a field called "AccountId" under it, nothing new here.

Re: Promote field to Sharepoint as a People and Groups datatype

Jaws01 — Thu, 02 Sep 2010 17:31:14 GMT

Yes I do have the People field to allow "Multiple Selections". I have the AccountIDs mapped to a single line of text. "john.doe \n\r mary.smith" (i.e. they appear on separate lines).

In the Workflow when I attempt to update the People group field I get a warning that => the lookup is not guaranteed to return a single valie, if more than one valie is returned only the first value will be be used, do you want to continue ? I said "Yes".

Re: Promote field to Sharepoint as a People and Groups datatype

KarenSL — Thu, 02 Sep 2010 16:22:44 GMT

I've not tried doing multiples but my food for thought are...did you make your people and group field in the list allow multiple selections? And, have you checked to see how the data is being promoted, meaning is it coming over as "john.doe; mary.smith" or some form of the account names separated in a way that SP likes?

If you get it working, let us know for future reference.

Thanks,

Karen.

Re: Promote field to Sharepoint as a People and Groups datatype

Jaws01 — Thu, 02 Sep 2010 16:00:08 GMT

Hi warrtalon,

I have the SPD workflow updating the People group column with an AccountID. However, this only seems to work when 1 user is selected. I need to make this work when multiple users are picked in the Contact Selector. Any ideas ? Thanks.

Re: Promote field to Sharepoint as a People and Groups datatype

davidevan — Wed, 04 Nov 2009 13:58:16 GMT

I followed the same steps you had outlined and I had outlined. I don't know why it never worked the first time because this is a pretty basic process. Either way it works now. In my workflow I ended up using the set field in current item action.

Re: Promote field to Sharepoint as a People and Groups datatype

warrtalon — Tue, 03 Nov 2009 23:07:05 GMT

Great! Glad it worked out. Other than starting from scratch, was there anything you did different that made it work? In your workflow, did you use set field in current item or update list item?

Re: Promote field to Sharepoint as a People and Groups datatype

davidevan — Tue, 03 Nov 2009 21:53:44 GMT

Thanks for all your help warrtalon and rbarath23. In the end I was able to use the AccountID and assign to the People/Group datatype. I started everything over (field promotion, people/group field creation. etc) and it worked good!

Re: Promote field to Sharepoint as a People and Groups datatype

rbarath23 — Tue, 03 Nov 2009 16:56:52 GMT

Did u promote AccountID(first)??

For a people Column, It will show all the columns that are string or Person Data Type or hyperlinks.. It wont show numbers and date.

This is weird and i can't get why it doesn't show up.

Re: Promote field to Sharepoint as a People and Groups datatype

warrtalon — Tue, 03 Nov 2009 15:49:31 GMT

It's best to use the User Profile Service and not the UIL, because downloading the entire UIL into your form could bring it to its knees if you have thousands of users. Even hundreds is slow compared to the UserProfileService, and the UIL is not populated with every user automatically.

Re: Promote field to Sharepoint as a People and Groups datatype

rbarath23 — Tue, 03 Nov 2009 15:44:56 GMT

As i said with the January Cumm Update, It works just for the email.

But if you use someother update or with SP2 or Aug Update you will be able to populate Domain\user name or just UserName or email address.

If you are using MOSS SP1 with January Update and have trouble populating the People field you can achieve that by Managed Code or a code-less method would be add the User Information List from the RootWeb or the CurrentWeb as a Data Source and use the rules to get the email of the selected user (AccountID)

Rule:

Create a datafield called Email with string in the Main data source and set the rule on the AccountID as

Condition:

When Accound is not blank

Email=@email(@login=AccountID) where email and login are fields from the Secondary data source and the follow the usual workflow procedure.

Re: Promote field to Sharepoint as a People and Groups datatype

warrtalon — Tue, 03 Nov 2009 15:44:04 GMT

The behavior you're seeing here is the same reason why we can't promote a text field straight into a People field - different data types. With SPD, I've always been able to push a string into the People field as long as it was the right string, which was an email address.

If you end up having to try for email address, then you'll need to use my blog on getting the current user's information without code, which you can do by using the current user's info (userName()) or another user's info by leveraging the AccountId value of a person chosen in a Contact Selector (just have to strip off the domain\ piece using a substring-after):

InfoPath - Get user information without writing code (extended)

Re: Promote field to Sharepoint as a People and Groups datatype

davidevan — Tue, 03 Nov 2009 15:38:17 GMT

warrtalon, you repsonded while I was typing. You basically outlined what I was trying to accomplish. I'll try this again from scratch.