We have a use case where we are using a list to orchestrate Meeting Minutes, in which, there is a repeating section for "Action Items." In this repeating section, there is "Item," "Responsible User(s)," and "Due Date." We want to generate an email to each "responsible user(s)" letting them know they're assigned an action item. I'm able to get the XML and parse it and everything works great as long as there aren't multiple users in the People Picker field. In the case of there being more than one responsible user for an item, we're fine with just sending one email to both (all) of them, I just can't "extract" that in a usable way.
Solved! Go to Solution.
When you get the individual user from the xml parsing, is it first saved as a person/group variable, then put into the Send Notification action?
If you add a PG (PersonGroup) variable it should be fine, if you add a collection of PG variables, it should also work, but when coming from an XML parsing, it may not be typed correctly. Everything seems as if a string unless you specifically convert the type.
Maybe just output the values you have in history and see if there is a type problem or format problem.
I tried the PG variable; it's like it can't read it. It only grabs the first person then a bunch of ;;; after, as though it knows there's "someone else" but can't do anything about it.
Line 1 is the XML raw, line 2 is the XML after the replacements (From Vadim's blog), line 3 is if I get the item from the collection (string of users) and assign it to a PG variable. You can see the trailing semicolons after Mark's name. There is another person in there, it's cut off by the character limit in the logging. Here's the full XML from the plaintext multi-line field I'm writing it to
I am having similar situation. How did you get rid of the characters before / after the email address? I just want to extract the email address but it comes withh the special characters and membership text. can you please help me with it?
Perfect, That was my next thought to have to extract them out. Great going to get this working and providing your solution!