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

Flow to populate look up field based on text field

Hello All,

 

I am working on 2 entities. 1st is Contact (Renamed as Donor) and 2nd is Orders (Renamed as Donation).

On Donation entity form, I have a system mandatory look up field called “Potential Customer” and text field “Email Address”. I want to populate Potential Customer field value based on Email Address set. This operation will look for email address from contact entity and return the customer name to Potential Customer Field.

I have followed above steps but seems to something missing. Thanks in advance.

 

Details.PNGDonor.PNGFlow Ex.PNG

 

Regards,
Logee

1 ACCEPTED SOLUTION

Accepted Solutions

Hi @Logee 

 

Use the Initialize Variable action to create a variable of type array.

 

In the No branch you create an Append to Array action and in the Value add the reference to the current record. 

At the very end add a Compose action and insert your array variable (if you want to see the result in the flow run) or add a Send Email  action and put the variable in the body. It will be ugly but at least you can see which items had multiple results.

 

Have you looked at merging the duplicate records? That would eliminate the issue of choosing which one to link 

View solution in original post

21 REPLIES 21

@Logee 

 

Are you trying to set the Potential Customer for the donation using the Flow when filling out the Donation form?

The Flow runs as a background process, not live when editing the form.

 

If you are looking for the flow to update the donation after saving, this won't work with Potential Customer being a required field. Change your Potential Donor field to Optional or Recommended.

 

 

Logee
Frequent Visitor

@bhitchlockfcs , Thanks for quick reply. I have tried changing field to Option although it didn't allow. It is mandatory field.

 

I am importing the data through plugin into Dynamics CRM and hence all the mapped fields are imported including email address.

Because Potential Customer field is look up, It isn't importing data and hence I thought to use Flow. 

 

Please refer to this post I have gone through to implement this:

 

https://diyd365.com/2019/03/12/update-a-lookup-from-a-text-field-no-code-solution/

Hi @Logee ,

 

Okay, makes sense with an import that the field would be empty importing via plugin. The guide you are following is using the old dynamics connector, not the current CDS one.

 

Fields in filters are case sensitive. You want to change it to emailaddress1 eq Email Address

 

Rather than the apply to each, create  a Condition using the expression length(outputs('List_records')?['body/value']) is equal to 1

This checks for a single matching contact, if there are duplicates or it does not exist it goes down the  No branch.

 

In the Yes branch you will want to create an Update Record and for the Potential Donor enter it as follows:

 

/contacts(outputs('List_records')?['body/value']?[0]?['contactid']) - This tells the Flow to use the field from the first (and only) result. 

 

To update a lookup in Flow with the Current Environment connector in general you need to prefix it with /<entity collection name>(<entityid>)

2020-08-23_15-14-54.png

2020-08-23_15-13-42.png

 

Hi @Logee ,

 

Just a minor correction in @bhitchlockfcs  emailaddress1 eq Email Address should be emailaddress1 eq 'Email Address'

 

Thanks

@bhitchlockfcs : That is very detailed description thanks.

 

As I am new to flows, trying to digest while I read through your post. 

 

I just have couple of questions. I  believe I have made suggested changes. 

 

1) To update a lookup in Flow with the Current Environment connector in general you need to prefix it with /<entity collection name>(<entityid>), Please check picture if I have correctly done:

 

3.PNG

 

 

2) Why we need to input to Contact (Contacts) field? OR you just set it to show an example for Potential Customer field?

 

Thanks in advance. Here are updated snapshots please let me know what other changes required:

 

1.PNG2.PNG

Thanks @ManishJain , I have kept it as emailaddress1 eq 'Email Address' as per your instructions. 

@bhitchlockfcs @ManishJain Currently below error coming up with suggested changes:

 

Error.PNG

Hi @Logee ,

 

You are putting value of Contact lookup value in account. Do you want to Update Customer or Potential Customer field in update record action ?

 

Thanks

@ManishJain : I want to update Potential Customer field value with Contact Details i.e., First Name + Last Name

 

I am sorry I didn't get what you mean by: "You are putting value of Contact lookup value in account."?

Hi @Logee ,

 

You should only put the value in Potential Customer as /contacts(guid) .

 

 

Thanks

@ManishJain It shows expression invalid. 

 

Also should I use Contacts or Accounts?

Hi @Logee 

 

You want to update the Customer(Contacts) 

 

It looks like Potential customer is linked to Accounts? If so you would need to switch to looking for the Account entity.

 

These type of Flows are fussy. Don't get frustrated, little things like a missing bracket or quotation mark can throw errors.

I find it helpful to add Compose actions and paste the same expression in there to view the results and verify it is doing what I intended.

 

@bhitchlockfcs I am not sure if "Potential Customer" is only linked to Accounts. Please check below image looks like it is linked to both Accounts and Contacts.

 

Potential Customer field.PNG

 

 "I find it helpful to add Compose actions and paste the same expression in there to view the results and verify it is doing what I intended." May I please know how to do that?

Seems to be one step close. Getting details needed. Error around update operation now. 

 

Flow.PNG

 

Customer Details.PNG

Hi @Logee 

 

You want to insert the Donation identifier into the Item ID, not account name. 

Potential Customer (Account) field should be in the format /accounts(<accountid>) where <accountid> is the unique identifier of the Account.

 

FYI - Customer is a special field in that it can be linked to either an Account or Contact. In the Flow it should show as two separate fields.

Hi @Logee ,

 

Customer can either be contact or account. You have to decide which of account or contact you want to set the lookup field with. If you go with Account use /accounts(guid) and if with contact use /contacts(guid) in potential customer. Since you are doing get record based on Contact email second option is preferred here. 

 

Thanks

@ManishJain @bhitchlockfcs : I have just managed to run first flow successfully. I can understand this whole operation better now. However, haven't understood the whole flow completely yet. Just copied and pasted so will study a bit more about it now. 

 

Thank you for your time and efforts in this matter. I am going to monitor now for next 24 hours and will keep you updated.

 

Thank you again. 

@ManishJain @bhitchlockfcs , Hello All.

 

After running a flow for a while, I can see it is working but there are some orders not capturing the contact details as below:

 

Not Captured.PNG

 

Yellow highlighted are not captured. What could be the reason? How to resolve.

In flow history, there are no failed flow run.

 

Regards,

Logee

Hi @Logee ,

 

The condition checking the length is true only when a single exact match is found. Otherwise it goes down the No branch. So it skips those records without failing.

Reasons for it being No are either:

a) There are multiple matches,

b) The email doesn't exist in the system

 

for case a) Add some logic here to decide which to use. If you create an Array variable and add an Append Array action in the No section and append the current record and then you can view/save/email the final result.

for case b) Use the Create Record action to add the Account.

 

Test for case a) length > 1

Test for case b) length = 0

 

 

 

 

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Kudoed Authors
Users online (4,131)