Using Base64 to Get Trigger Output

[robgar]

I have the following flow that WORKS when I use a manual trigger.  When I use the same flow actions on a MSFT Form trigger, it fails.  I am ignorant on how to use base64 decoding (I got help just to make this solution work).  Any idea on how to alter this Compose action to accept a MSFT Form field Email (text) so that I can make this UPN assignment to a O365 group work?

[DeepakS]

Hi @robgar 

You need get the Email (Text) field value from Form , once Form submitted and pass that to Get User Profile action to get the all details.

Here is an working example::

Regads,

DS

[robgar]

@DeepakS I wish it were that simple. I do get the form details earlier in the flow, but simply adding the Email field from the form doesn't work and I think it has something to do with the format of the field.   See this thread that I started a few weeks ago, where the only way to fix the error in the condition was to use a decodebase64 expression, but I was using a manual trigger in that case:  https://powerusers.microsoft.com/t5/Building-Flows/Condition-Causes-Add-User-to-Group-to-Fail/m-p/58...

In using your suggestion, it brings in the correct Email address, but it claims the user is not found (which is incorrect).  This same error was happening to me until I used decodebase64.

[DeepakS]

Hi @robgar 

I just did a quick test to add member to group with email comes from Form ,  Where you getting error?

 

[robgar]

It's strange.  I get it inside of the Condition.  I have not retested it outside of the Condition, but when I was having the issue previously it worked outside of it no problem.  The Condition is simple .. it looks at the value in a form field and if true it runs the positive side of the flow that I showed you.  In this case, it finds the correct email value, but using that value it cannot locate the user profile.  

[DeepakS]

Hi @robgar 

Try to add a compose to see what value passing to Get User Profile, before get user profile action. this may give some idea on whats wrong.

Regards,

DS

[robgar]

I just rebuilt the flow and removed the Condition.  I cannot get past the Get User Profile error.  Again, I recall these exact issues with the manual trigger that were fixed with using decodebase64.  Problem is that my decodebase64 code as it's written fails with MS Forms and I don't know how to adjust it.

Example Failure

1. Input = MS Form with text field called "Email" (use inputs username@domain.com)
2. Action = New User gets created (successfully)
3. Email (UPN) value is passed to Get User Profile (fails)

Here is Flow & Error & Proof of User (I have tried various values in Get Profile including output of the Compose .. no change)

[DeepakS]

Hi @robgar 

Oh , I did not noticed that you are actually creating user account and adding it to group.

Actually if you are creating account, you can pass the UserPrinciple that you get in "Create User" action  to the "Add Member " action, give a try it should work.

[robgar]

I suppose my instance is haunted ...

The source resource object or one of the objects being referenced do not exist.

In the Flow below, I am passing the Email from the form into the UPN .. is this causing an issue with the value??

[DeepakS]

Hi @robgar 

Interesting, i create a sample flow similar to whats in your Flow and it works for me.

dumb question - have you tried adding to any other group?

Regards,

Deepak

[robgar]

Thing is .. it's not getting to that point .. it's failing at Get Profile.

[DeepakS]

Hi @robgar  As i explained if you are creating user in flow then want to add that user to Group , you don't need Get User Profile action, because  create user action will provide all the details of newly created user.

[robgar]

True that.  I will try a new group, but like I mentioned, it works when I used decodebase64 and a manual trigger.  Hmm.  I'll keep searching for and answer. really appreciate your assistance.

[robgar]

@DeepakS One more update ..

I removed the condition and put in a Switch.  The action in the case only adds a member to a group (and I've tried several different groups).  The first time I ran the test, it worked!  Yet every time after it didn't.  Makes no sense to me.  Here is the construct of the current flow, along with the error.  I  still believe strongly that this has to do with the format of the Email being passed into the add to group action as a UPN.  In my working manual trigger flow, the decodebase64 code takes the email string and passes it to Get User which then passes it to Add Member.  I agree that those are extra steps, but they seem necessary for the base64 decoding handoffs.  Problem is, I have no idea how to code the base64 expression for MS Form vs the manual trigger.

Base64 expression that works in manual trigger flow.

decodeBase64(triggerOutputs()['headers']['x-ms-user-email-encoded']

This Code works in Manual Trigger Flow

Current MS Form Flow

ERROR in MS Form Trigger Form:

Invalid target for navigation property update. URI must target an entity.

Hoping this provides more insight.  Appreciate any assistance I can get.

[v-litu-msft · Accepted solution]

Hi @robgar,

Thank you for your invite, the reason for the manually trigger should use decodeBase64() function is the Email field from manually trigger is a string of base64 code, just like as below:

But the User(UPN) field of Get User profiles action requires User principal name or Email, it should be string type, so we should use decodeBase64() function to convert it into a string.

So I assume that whether the error will occur is caused by the Email isn't realized a string, you could try to use a string() function convert the Email get from MS form, then put output of string() function into Get user profiles action.

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[robgar]

Thank you for joining the conversation, @v-litu-msft .  Unfortunately, the string function is not working either.  The flow output gives every indication that it is passing the right info, but it still errors.  I have tried several different iterations of the below with no success.

The below expression uses the Email field within the MS Form.  The error is user not found, but the user is clearly found in the O365 admin console.

string(body('Get_response_details')?['r6580f1c18a6f46e0be4ffc9d759e6444'])

[v-litu-msft]

Hi @robgar,

Could you find the user in the Azure AD?

How about you create a new test Email to Get user profiles?

Best Regards,
Community Support Team _ Lin Tu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[robgar · Accepted solution]

Okay, I had a hunch based on your suggestion to look at the AD as well, and it worked.  Delay the flow.

Whenever I looked at the O65 Admin or Azure AD, the user is there.  BUT, I wondered if the flow was moving to fast for the record to be completely written and therefore errors out ... so I kept refreshing the AD and the user was slow to appear and the flow errored.  I inserted a 10 second delay after user creation and voila!  I'm going to play with the timing, but this was the first time it actually worked!  I'm also going to back out the string expression to simplify the steps a bit now knowing what I know.