cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Frequent Visitor

Flow grabs wrong value from choice field

Hello Everyone,

 

The flow we have is grabbing the wrong value of a choice field.

When a record is created in ListA we would like to have a similar record created in ListB

 

Sharepoint ListA (Repairs)

Serial# - text

Model# - text

Client ID - choice  (10 choices in dropdown)

 

Sharepoint ListB (Status)

Serial - text

Client ID - choice (10 choices in dropdown)

 

When the flow runs it gets the serial number correctly just fine but the Client ID value is the wrong one.

It appears to grab the Client Code below the one that is chosen.

 

Attached is a screenshot of the flow.

Any assistance is appreciated.

Thank you.

 

Flow.PNG

 

1 ACCEPTED SOLUTION

Accepted Solutions
Super User III
Super User III

@lakosked 

If you want the Client ID column in list B to match what is in List A then you should be selecting "Client ID Value" from Dynamic properties for List A as the input for List B. 

 

 

 

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Scott

View solution in original post

3 REPLIES 3
Super User III
Super User III

@lakosked 

If you want the Client ID column in list B to match what is in List A then you should be selecting "Client ID Value" from Dynamic properties for List A as the input for List B. 

 

 

 

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.

Scott

View solution in original post

Community Support
Community Support

 

Hi @lakosked ,

 

I agree with @ScottShearer that if the field type is choice, we should configure the Choice Value in the corresponding field.

 

If the field is a lookup column, we may need to use the column id.

 

Please take a try again and feel free to let us know if the issue still exists.

 

Best Regards,

Community Support Team _ Barry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Frequent Visitor

Hello Everyone.

And thank you all for your replies.

They were helpful in that you pointed to "value".

 

This caused further digging to that field specifically which then pointed to the error.

The ClientID was getting pulled from a 3rd table in SP that was not a one to one relationship.

It was a 3rd table we didn't notice due to its name.  At any rate, this caused the table to have more entries than the original data.

 

Once this was discovered, we pointed the flow to the correct table with the client ID and now things are lining up.

Thanks again.

Helpful resources

Announcements
New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

MPA Community Blog

Power Automate Community Blog

Check out the community blog page where you can find valuable learning material from community and product team members!

Users online (99,039)