Person or Group field rules getting triggered

[Amal Vellappillil]

Hi Alex,

Using v1,2,7
I am running into the following issue.

Bug #1
——-
Rule
AND
– Field 1 (Person or Group field – single) changed from initial value
– Field 2 (text) is not “sample text”
TRUE – > send and email

I changed Field 2 value in edit form and it triggered the email. When I debugged the rule I saw that “changed from initial value” condition is true (nothing was changed). So i tried adding the “is changed” condition as well. The debug shows that the following (for person or group field – this field was not changed)
is changed = TRUE
is changed from initial value = TRUE

I tested these conditions with a text field and it seems to work as expected. However, person or group field type is not behaving as expected. I haven’t tried the other field types either.

Bug #2/Feature behaviour
————————-
I noticed that some times “is changed” and “is changed from initial value” is getting triggered when the value is <NULL> when the form loads. But after the form is loaded, the value changes from <NULL> to <blank> (this change happens automatically – not triggered by a user input). Can the “is changed” and “is changed from initial value” conditions handle such data conditions behind the scenes and trigger only if its a valid value change? I noticed this mainly due to migrating data from SharePoint onpremise to SharePoint online using ShareGate.

Thank you

[Alexander Bautz]

Hi,
I’m not able to recreate these issues so my guess is that it is ShareGate that caused the issue by adding the text “null” or something to the value of the list item when you migrated. Are you able to reproduce it on a list item that has been edited and saved after the migration?

I might be able to fix it in the code if you can provide me with some information.

On one item that has not been edited after the migration, open the item in EditForm and open the developer tools by hitting F12 (and select “Open devtools” if in Edge). Now go to the console tab and type in this and hit Enter:

dffs_beforeProperties

Expand and take a screenshot of the section with the field in question. The field name will be on this format (example with AssignedTo):

AssignedToId: value_goes_here
AssignedToStringId: value_goes_here

Now do the same by typing in this:

dffs_fieldValueHistory

Expand and take a screenshot of the value associated with your field name.

Alexander

[Amal Vellappillil]

Attached is the information you requested for.

Attachments:

1. 

   dffs_before_properties_fieldvaluehistory.jpg
   

[Alexander Bautz]

Thanks,
It looks the same in my test, but I don’t get the same behavior as you. Can you show me a screenshot of the rule setup for the #1 scenario in your original post and of the console debug output? – activate debug on the rule and see the output in the dev tools console tab.

Alexander

[Amal Vellappillil]

Alex,
I have attached the information you requested.

This time I am noticing the rule is not getting triggered when its empty, its getting triggered when it has some data to begin with. I apologize for the confusion. The attached image should show the rule status on both conditions. I hope this helps.

[Amal Vellappillil]

Alex, I had sent the attachment via email since the forum couldnt upload it. Can you please confirm if you got it?

[Alexander Bautz]

Yes, I got the email and have reproduced the problem. I’ll get it fixed in the next version over the weekend.

Alexander

[Amal Vellappillil]

Ok. Thank you for confirming.

[Author]

Posts