Set Value action for People or group field type

[Amal Vellappillil]

Hi, I am trying to use the Set Field Value action available in the rules to set the value of a Person or Group (multi value) field. The rule is getting data from field1 and setting value in field2. When I type in the first person’s name and select that person, field2 value gets populated as expected. When I type in a second person’s name and select that person, field2 does not get updated. I see an error in dev console:
https://xxxx.sharepoint.com/sites/Intranet/_api/web/siteUsers/getByEmail(‘%20xxxxx@xxxx’) 404 (Not Found)

As you can see there is a %20 in front of the actual email address and because of that user is not found. So this seems like a bug. Can you look into this?

I also tried to use the setFieldValue function, but that didnt work either. With this there were no errors in dev console. I tried different ways to use this function from js.
– setFieldValue(‘field2’, getFieldValue(‘field1’); <– this didnt work at all.
– I tried using a for loop to iterate over values from ‘field1’ and tried setFieldValue(‘field2’, values[i].email). <– this updated field2 with the first person from field1, but second person was not brought over.
How do you use this setFieldValue function in this case?

[Amal Vellappillil]

I dont know why there is a &#8217 at the end of the url, but the actual url is as follows:
https://xxxx.sharepoint.com/sites/Intranet/_api/web/siteUsers/getByEmail(‘%20xxxxx@xxxx&#8217;)

[Alexander Bautz]

Are both Field1 and Field2 multichoice? Can you email me a screenshot of the rule you use to set the values?

Alexander

[Alexander Bautz]

No need to send anything – I found the problem and will fix it in the next release (probably sometime next week).

Alexander

[Amal Vellappillil]

Hey Alex, any update on when the next update will be available with these fixes?

[Alexander Bautz]

I have a few other issues left before I can release the next version, but hope to get it done during the weekend.

Alexander

[Amal Vellappillil]

Ok, thank you for the update.

[Amal Vellappillil]

Hi Alex,

I see that a fix was provided for this issue in version 1.0.73. However, I feel like its only partially fixed. Here is the behavior I am seeing:
– Field1 is people picker field, Field2 is people picker field.
– Rule set field value (field1 is changed set the value in field2 from field1)
– When people are added to field1, they are getting added to field2
– When people are removed from field1, they are not removed from field2 (this feels like a bug)
– Only when everyone has been removed from field1, everyone gets removed from field2

Right now I am getting around this by running two set field value actions in the rule.
– First set field2 to blank
– Then set field2 to field1 values.

Thank you for all your work on this and I hope a fix will be issued in the next release, so the feature works in the most natural form than going through work arounds.

[Alexander Bautz]

Hi,
Are both of your people picker fields multichoice?

Alexander

[Amal Vellappillil]

Yes they are both people picker fields with multichoice.

[Alexander Bautz]

I have added a new option “Clear the previous value before setting new value” to the Set field value action in the rule-builder.

Alexander

[Amal Vellappillil]

Thank you so much, this is working as expected now.

[Author]

Posts