cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Holly_CMS
Responsive Resident
Responsive Resident

Need to get the value from lookup table

Hi All:

 

I have an approval flow set up. However, I noticed it is NOT pulling the email address from the main list despite the fact it is in the list from the lookup table.

EmailJoinIssue.pngEmailJoinIssue3.pngEmailJoinIssue2.png

I tried a couple tricks from posts here but not the same scenarios as this one. 

 

Please assist.

 

Thank you!

Holly

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

I made an example that has a lot of photos about the SharePoint lists and columns. The actual flow example is only showing about selecting the dynamic content and the outputs. So the flow part is relatively short.

 

I want to focus on the SharePoint columns and settings because I think that would be where the problem could be created.

 

So basically go down and look at the simple flow and see if that helps. If it does not, then look through my SharePoint list columns and details and see if you can recognize the difference between yours and mine. That should help narrow down what could cause the problem.

 

Example:

In my example I have a Patient Referral sharepoint list that I will add a new patient/create new item whenever I get a phone call. When a new patient is added, I have to select what clinic I referred them to. I use the "AssignedToClinic" lookup column to select the clinic that is in the source ClinicList. This will get all of the details of the clinic and pull it into my patient referral list. My flow is triggered whenever a new item is created in the Patient Referral list.

 

Source of Lookup Column - Clinic List

I created a SharePoint list called ClinicList. This basically shows clinics and the managing people. This list will be the source used by the lookup column in the second list.

Lookup Source Clinic List - The Clinic List is basically flat text values that will be the source of the lookup in the second list.Lookup Source Clinic List - The Clinic List is basically flat text values that will be the source of the lookup in the second list.Lookup Source Clinic List - List Settings and Column TypesLookup Source Clinic List - List Settings and Column Types

 

Main List Used for Flow - Patient Referral

The second list will be the one used by people to trigger flows and everything.

Main Action List Patient Referral - This is used by people and will have the lookup column that references the first ClinicListMain Action List Patient Referral - This is used by people and will have the lookup column that references the first ClinicListMain Action List Patient Referral - List Settings Column TypesMain Action List Patient Referral - List Settings Column Types

 

The Patient Referral list appears to have 7 Lookup type columns. But really I only added 1 Lookup column "AssignedToClinic" to the list. This is the primary lookup column where I will select the clinic. The secondary lookup columns are automatically applied because I checked the Show Additional Fields in the column settings.

The Lookup column AssignedToClinic will be the primary selection in the Patient Referral list, but additional fields are linked to this columnThe Lookup column AssignedToClinic will be the primary selection in the Patient Referral list, but additional fields are linked to this column

 

So when I create a new item in the Patient Referral list, I have to select the AssignedToClinic in the dropdown for the lookup. None of the other columns are edited when a new item is created.

But when I create the new item, all of the secondary linked lookup columns are filled in automatically.

Patient Referral List - Create a new item only requires selecting the AssignedToClinic lookup value.Patient Referral List - Create a new item only requires selecting the AssignedToClinic lookup value.When the new item is created all of the secondary columns are automatically filledWhen the new item is created all of the secondary columns are automatically filled

 

My basic flow is triggered when a new item is created in the Patient Referral list. This will show the separate value types that can be returned from the lookup column. My example only shows the AssignedToClinic dynamic content, but the results will be the same if I used any of the other lookup columns.

 

Dynamic Content Options:

AssignedToClinic Id - will be the ClinicList Item Id of the lookup value selected in the Patient Referral list

AssignedToClinic Value - will be the text string output of the lookup value

AssignedToClinic - will be the full object of the lookup value

 

There are 3 separate Dynamic Content options for each lookup fieldThere are 3 separate Dynamic Content options for each lookup fieldScroll through the dynamic content to see each of the optionsScroll through the dynamic content to see each of the optionsThe results of the flow show the outputs for each type of dynamic content optionThe results of the flow show the outputs for each type of dynamic content option

 

So please look this over and see if it helps you get the correct output. You want to select the dynamic content that ends with "Value" in order to get the single text output.

 

If you are getting different results than my example please let me know where you see the differences in column types or what is in your flow.

View solution in original post

21 REPLIES 21

So what is it pulling in with the dynamic content? Can you put it into a compose step, run the flow, and see what the output is?

 

Also can you show the dynamic content you are selecting? 

 

Lookup will have 2 options. One will be like "CM_EmailAddress Id" and the other would be "CM_EmailAddress Value" and the one with value would be the email address.

Hi Wskinnermctc...

 

and I tried both. Did not work. Let me do the compose - brb.

 

Thanks 🙂

From the Main list - there are 3 CM_address values from the Dynamics. 

"{\"@odata.type\":\"#Microsoft.Azure.Connectors.SharePoint.SPListExpandedReference\"
,\"Id\":39,\"Value\":\"holly.cathcart@XXXXXXXXX.com\"}
\nholly.cathcart@XXXXXXXX.com\n39"

 

EmailJoinIssue4.png

 

From the look up List...

EmailJoinIssue5.png

Hence why I need to somehow add the lookup list into the flow and pull from there for the CM address.

 

 

Ok, I can't reproduce your issue because I can't get Person type columns to lookup across lists. (I also can't get a Person Type column to only display an email address in the SP List like yours, mine will only show the person's name.)

You must be doing something extra that I don't understand.

 

Can you explain the types of columns in each list and how you are getting the data filled in? Like which columns are Person Type and if you are doing any calculated column or posting data into the column to create the item.

 

I made a narrative below to help me understand. Please edit this to be correct so I have the information.

Main List - SEED Merf Tickets - This is a list where new SEED Tickets are added. Whenever a new Seed ticket is added, the user selects a clinic. The approvals in the flow are being run from each new SEED ticket added to this list.
Columns in Main SEED Merf Tickets:
ClinicManager - This is a text type column where the Clinic Manager's name is typed in.
CM_EmailAddress - This is a lookup column that is using the something to lookup the email address from the MERFClinicQMCList

 

Lookup Source List - MERFClinicQMCList - This has a list of clinics and each clinic has a Clinic Manager

Columns in MERFClinicQMCList:
ClinicManager - This is a text type column where the Clinic Manager's name is typed in
CM_EmailAddress - This is an email type column?

 

I'm trying to reproduce your lists so I can test the issue, but I can't get mine set up like yours.

Actually, you are close but the data in the main list is already filled by the SQL Server flow. Lookup list already has the CM and RD email addresses in there. There is no data input in the main nor lookup lists from anyone.

 

The CM email address (and other email addresses fields) is a single line of text, actually. 

 

Pretty cut and dry. 

 

So, in the approval action, I have it customed to add 3 options for the staff and/or CM to select. The lookup list is not in the flow and I need to add it in there so that Teams can send the CM the customed approval to select one of the three options. But it is not sending it to CM. Only to the User Email address from the main list as the main list is in the flow. 

 

EmailJoinIssue.png

 

Hope this clarifies for you 🙏

 

 

This is where I am at so far and I am stuck at the Parse JSON...It's throwing an error doesn't make sense....

 

EmailJoinIssue6.pngEmailJoinIssue7.png

 

 

What is the source for the ParseJSON? I'm assuming the Select outputs will be the source for the ParseJSON.

 

How did you create the Schema for the ParseJSON? 

 

The input Content of the ParseJSON looks like the "Clinic Manager" value, which itself is an array, is probably throwing off the ParseJSON schema.

 

I think we still aren't on the same page, (or at least I am not). And this is making this more complicated than it has to be.

I also think your problem can be resolved easily, but I need to reproduce what you are doing to get the solution.

 

I want to duplicate your SharePoint lists. So I can make a version to test.

 

Can you show me the columns and column types from each of the SharePoint lists from the column settings?

 

(I know this current flow is not populating either of the SharePoint lists. I was trying to understand how the lists were being populated before this current flow is triggered. But disregard telling me any of that information, I just need to know the columns and column types.)

Ok The Main list is looooong but see the highlighted...EmailJoinIssue10.pngEmailJoinIssue8.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

The look up list

 

EmailJoinIssue9.png

And the source of the parse JSON is the Select - yes However, if you have a better way of doing this - be my guest 🙂 

 

Just FYI I took out the Clinic Manager but it is still throwing out the requirements needed error...This is from the Parse JSON Schema

 

{
    "type""array",
    "items": {
        "type""object",
        "properties": {
            "@@odata.etag": {
                "type""string"
            },
            "ItemInternalId": {
                "type""string"
            },
            "ID": {
                "type""integer"
            },
            "Title": {
                "type""string"
            },
            "CaseNotesID": {
                "type""string"
            },
            "Level": {
                "type""integer"
            },
            "Ticket_Status": {
                "type""object",
                "properties": {
                    "@@odata.type": {
                        "type""string"
                    },
                    "Id": {
                        "type""integer"
                    },
                    "Value": {
                        "type""string"
                    }
                }
            },
            "Ticket_Status#Id": {
                "type""integer"
            },
            "State": {
                "type""string"
            },
            "Clinic": {
                "type""string"
            },
            "Methasoft_ID": {
                "type""string"
            },
            "PatientName": {
                "type""string"
            },
            "Entered_By": {
                "type""string"
            },
            "NotesEnteredDate": {
                "type""string"
            },
            "UserEmailAddress": {
                "type""string"
            },
            "Email_Status": {
                "type""object",
                "properties": {
                    "@@odata.type": {
                        "type""string"
                    },
                    "Id": {
                        "type""integer"
                    },
                    "Value": {
                        "type""string"
                    }
                }
            },
            "Email_Status#Id": {
                "type""integer"
            },
            "EmailHistory": {
                "type""string"
            },
            "Note_Date": {
                "type""string"
            },
            "BU": {
                "type""integer"
            },
            "CN_Type": {
                "type""string"
            },
            "Minutes": {
                "type""integer"
            },
            "NoteText": {
                "type""string"
            },
            "Staff_Response": {
                "type""string"
            },
            "Characters": {
                "type""integer"
            },
            "CharPerMin": {
                "type""integer"
            },
            "Short_Counseling": {
                "type""string"
            },
            "HighCharLowTime": {
                "type""string"
            },
            "LowCharHighTime": {
                "type""string"
            },
            "NoContactWith": {
                "type""string"
            },
            "LongTimeNoUnits": {
                "type""string"
            },
            "AZFocusArea": {
                "type""string"
            },
            "ZeroUnits": {
                "type""string"
            },
            "HighMinutes": {
                "type""string"
            },
            "NegativeMinutes": {
                "type""string"
            },
            "MontanaZeroBU": {
                "type""string"
            },
            "DuplicateNoteType": {
                "type""string"
            },
            "HighUnits": {
                "type""string"
            },
            "LateEntry": {
                "type""string"
            },
            "StartWorkflow": {
                "type""string"
            },
            "ClinicManagement_x003a_ClinicMan": {
                "type""object",
                "properties": {
                    "@@odata.type": {
                        "type""string"
                    },
                    "Id": {
                        "type""integer"
                    },
                    "Value": {
                        "type""string"
                    }
                }
            },
            "ClinicManagement_x003a_ClinicMan#Id": {
                "type""integer"
            },
            "ClinicManagement_x003a_CM_EmailA": {
                "type""object",
                "properties": {
                    "@@odata.type": {
                        "type""string"
                    },
                    "Id": {
                        "type""integer"
                    },
                    "Value": {
                        "type""string"
                    }
                }
            },
            "ClinicManagement_x003a_CM_EmailA#Id": {
                "type""integer"
            },
            "ClinicManagement_x003a_RegionalD": {
                "type""object",
                "properties": {
                    "@@odata.type": {
                        "type""string"
                    },
                    "Id": {
                        "type""integer"
                    },
                    "Value": {
                        "type""string"
                    }
                }
            },
            "ClinicManagement_x003a_RegionalD#Id": {
                "type""integer"
            },
            "ClinicManagement_x003a_AssignedQ": {
                "type""object",
                "properties": {
                    "@@odata.type": {
                        "type""string"
                    },
                    "Id": {
                        "type""integer"
                    },
                    "Value": {
                        "type""string"
                    }
                }
            },
            "ClinicManagement_x003a_AssignedQ#Id": {
                "type""integer"
            },
            "ClinicManagement_x003a_RD_EmailA": {
                "type""object",
                "properties": {
                    "@@odata.type": {
                        "type""string"
                    },
                    "Id": {
                        "type""integer"
                    },
                    "Value": {
                        "type""string"
                    }
                }
            },
            "ClinicManagement_x003a_RD_EmailA#Id": {
                "type""integer"
            },
            "ClinicManagement_x003a_QMC_Email": {
                "type""object",
                "properties": {
                    "@@odata.type": {
                        "type""string"
                    },
                    "Id": {
                        "type""integer"
                    },
                    "Value": {}
                }
            },
            "ClinicManagement_x003a_QMC_Email#Id": {
                "type""integer"
            },
            "ErrorTypes": {
                "type""string"
            },
            "CaseNoteIDPlus": {
                "type""string"
            },
            "ClinicManagement_x003a_Methasoft": {
                "type""object",
                "properties": {
                    "@@odata.type": {
                        "type""string"
                    },
                    "Id": {
                        "type""integer"
                    },
                    "Value": {
                        "type""string"
                    }
                }
            },
            "ClinicManagement_x003a_Methasoft#Id": {
                "type""integer"
            },
            "ClinicManagement": {
                "type""object",
                "properties": {
                    "@@odata.type": {
                        "type""string"
                    },
                    "Id": {
                        "type""integer"
                    },
                    "Value": {
                        "type""string"
                    }
                }
            },
            "ClinicManagement#Id": {
                "type""integer"
            },
            "Modified": {
                "type""string"
            },
            "Created": {
                "type""string"
            },
            "Author": {
                "type""object",
                "properties": {
                    "@@odata.type": {
                        "type""string"
                    },
                    "Claims": {
                        "type""string"
                    },
                    "DisplayName": {
                        "type""string"
                    },
                    "Email": {
                        "type""string"
                    },
                    "Picture": {
                        "type""string"
                    },
                    "Department": {},
                    "JobTitle": {}
                }
            },
            "Author#Claims": {
                "type""string"
            },
            "Editor": {
                "type""object",
                "properties": {
                    "@@odata.type": {
                        "type""string"
                    },
                    "Claims": {
                        "type""string"
                    },
                    "DisplayName": {
                        "type""string"
                    },
                    "Email": {
                        "type""string"
                    },
                    "Picture": {
                        "type""string"
                    },
                    "Department": {},
                    "JobTitle": {}
                }
            },
            "Editor#Claims": {
                "type""string"
            },
            "{Identifier}": {
                "type""string"
            },
            "{IsFolder}": {
                "type""boolean"
            },
            "{Thumbnail}": {
                "type""object",
                "properties": {
                    "Large": {},
                    "Medium": {},
                    "Small": {}
                }
            },
            "{Link}": {
                "type""string"
            },
            "{Name}": {
                "type""string"
            },
            "{FilenameWithExtension}": {
                "type""string"
            },
            "{Path}": {
                "type""string"
            },
            "{FullPath}": {
                "type""string"
            },
            "{HasAttachments}": {
                "type""boolean"
            },
            "{VersionNumber}": {
                "type""string"
            }
        },
        "required": [
            "@@odata.etag",
            "ItemInternalId",
            "ID",
            "Title",
            "CaseNotesID",
            "Level",
            "Ticket_Status",
            "Ticket_Status#Id",
            "State",
            "Clinic",
            "Methasoft_ID",
            "PatientName",
            "Entered_By",
            "NotesEnteredDate",
            "UserEmailAddress",
            "Email_Status",
            "Email_Status#Id",
            "EmailHistory",
            "Note_Date",
            "BU",
            "CN_Type",
            "Minutes",
            "NoteText",
            "Staff_Response",
            "Characters",
            "CharPerMin",
            "Short_Counseling",
            "HighCharLowTime",
            "LowCharHighTime",
            "NoContactWith",
            "LongTimeNoUnits",
            "AZFocusArea",
            "ZeroUnits",
            "HighMinutes",
            "NegativeMinutes",
            "MontanaZeroBU",
            "DuplicateNoteType",
            "HighUnits",
            "LateEntry",
            "StartWorkflow",
            "ClinicManagement_x003a_ClinicMan",
            "ClinicManagement_x003a_ClinicMan#Id",
            "ClinicManagement_x003a_CM_EmailA",
            "ClinicManagement_x003a_CM_EmailA#Id",
            "ClinicManagement_x003a_RegionalD",
            "ClinicManagement_x003a_RegionalD#Id",
            "ClinicManagement_x003a_AssignedQ",
            "ClinicManagement_x003a_AssignedQ#Id",
            "ClinicManagement_x003a_RD_EmailA",
            "ClinicManagement_x003a_RD_EmailA#Id",
            "ClinicManagement_x003a_QMC_Email",
            "ClinicManagement_x003a_QMC_Email#Id",
            "ErrorTypes",
            "CaseNoteIDPlus",
            "ClinicManagement_x003a_Methasoft",
            "ClinicManagement_x003a_Methasoft#Id",
            "ClinicManagement",
            "ClinicManagement#Id",
            "Modified",
            "Created",
            "Author",
            "Author#Claims",
            "Editor",
            "Editor#Claims",
            "{Identifier}",
            "{IsFolder}",
            "{Thumbnail}",
            "{Link}",
            "{Name}",
            "{FilenameWithExtension}",
            "{Path}",
            "{FullPath}",
            "{HasAttachments}",
            "{VersionNumber}"
        ]
    }
}

 

 

Thank you,

Holly

The error message from the Output of the Parse JSON 

 

{
    "errors": [
        {
            "message""Required properties are missing from object: @OData.etag, ItemInternalId, ID, Title, CaseNotesID, Level, Ticket_Status, Ticket_Status#Id, State, Clinic, Methasoft_ID, PatientName, Entered_By, NotesEnteredDate, UserEmailAddress, Email_Status, Email_Status#Id, EmailHistory, Note_Date, BU, CN_Type, Minutes, NoteText, Staff_Response, Characters, CharPerMin, Short_Counseling, HighCharLowTime, LowCharHighTime, NoContactWith, LongTimeNoUnits, AZFocusArea, ZeroUnits, HighMinutes, NegativeMinutes, MontanaZeroBU, DuplicateNoteType, HighUnits, LateEntry, StartWorkflow, ClinicManagement_x003a_ClinicMan, ClinicManagement_x003a_ClinicMan#Id, ClinicManagement_x003a_CM_EmailA, ClinicManagement_x003a_CM_EmailA#Id, ClinicManagement_x003a_RegionalD, ClinicManagement_x003a_RegionalD#Id, ClinicManagement_x003a_AssignedQ, ClinicManagement_x003a_AssignedQ#Id, ClinicManagement_x003a_RD_EmailA, ClinicManagement_x003a_RD_EmailA#Id, ClinicManagement_x003a_QMC_Email, ClinicManagement_x003a_QMC_Email#Id, ErrorTypes, CaseNoteIDPlus, ClinicManagement_x003a_Methasoft, ClinicManagement_x003a_Methasoft#Id, ClinicManagement, ClinicManagement#Id, Modified, Created, Author, Author#Claims, Editor, Editor#Claims, {Identifier}, {IsFolder}, {Thumbnail}, {Link}, {Name}, {FilenameWithExtension}, {Path}, {FullPath}, {HasAttachments}, {VersionNumber}.",
            "lineNumber"0,
            "linePosition"0,
            "path""[0]",
            "value": [
                "@odata.etag",
                "ItemInternalId",
                "ID",
                "Title",
                "CaseNotesID",
                "Level",
                "Ticket_Status",
                "Ticket_Status#Id",
                "State",
                "Clinic",
                "Methasoft_ID",
                "PatientName",
                "Entered_By",
                "NotesEnteredDate",
                "UserEmailAddress",
                "Email_Status",
                "Email_Status#Id",
                "EmailHistory",
                "Note_Date",
                "BU",
                "CN_Type",
                "Minutes",
                "NoteText",
                "Staff_Response",
                "Characters",
                "CharPerMin",
                "Short_Counseling",
                "HighCharLowTime",
                "LowCharHighTime",
                "NoContactWith",
                "LongTimeNoUnits",
                "AZFocusArea",
                "ZeroUnits",
                "HighMinutes",
                "NegativeMinutes",
                "MontanaZeroBU",
                "DuplicateNoteType",
                "HighUnits",
                "LateEntry",
                "StartWorkflow",
                "ClinicManagement_x003a_ClinicMan",
                "ClinicManagement_x003a_ClinicMan#Id",
                "ClinicManagement_x003a_CM_EmailA",
                "ClinicManagement_x003a_CM_EmailA#Id",
                "ClinicManagement_x003a_RegionalD",
                "ClinicManagement_x003a_RegionalD#Id",
                "ClinicManagement_x003a_AssignedQ",
                "ClinicManagement_x003a_AssignedQ#Id",
                "ClinicManagement_x003a_RD_EmailA",
                "ClinicManagement_x003a_RD_EmailA#Id",
                "ClinicManagement_x003a_QMC_Email",
                "ClinicManagement_x003a_QMC_Email#Id",
                "ErrorTypes",
                "CaseNoteIDPlus",
                "ClinicManagement_x003a_Methasoft",
                "ClinicManagement_x003a_Methasoft#Id",
                "ClinicManagement",
                "ClinicManagement#Id",
                "Modified",
                "Created",
                "Author",
                "Author#Claims",
                "Editor",
                "Editor#Claims",
                "{Identifier}",
                "{IsFolder}",
                "{Thumbnail}",
                "{Link}",
                "{Name}",
                "{FilenameWithExtension}",
                "{Path}",
                "{FullPath}",
                "{HasAttachments}",
                "{VersionNumber}"
            ],
            "schemaId""#/items",
            "errorType""required",
            "childErrors": []
        }

Ok thank you, I'm working on an example.


Do you have a reason for the Main List lookup columns to all be separate? Or did you use a single lookup column and renamed the additional columns so they didn't have that leading name?

 

wskinnermctc_0-1697046460710.png

Single Lookup Column Settings.png

 

Like in my example here, my SP List really only has 1 lookup column "AssignedToClinic" which will have an option selected using the Title from the lookup list. The rest of the columns are part of that single look up column.

 

Just want to double check that I'm looking at your list correctly.

It was because the columns weren't appearing in the main list for some odd reason...so I had to select these. Give me a few moments to think why as it's been a couple months I did this. I believe it was because the title of the look up is not the same as the main one....🤔

Can you show me your settings of the two columns "Clinic Manager" and "CM_EmailAddress"?

You mean this one from the main list?

 

EmailJoinIssue11.png

I made an example that has a lot of photos about the SharePoint lists and columns. The actual flow example is only showing about selecting the dynamic content and the outputs. So the flow part is relatively short.

 

I want to focus on the SharePoint columns and settings because I think that would be where the problem could be created.

 

So basically go down and look at the simple flow and see if that helps. If it does not, then look through my SharePoint list columns and details and see if you can recognize the difference between yours and mine. That should help narrow down what could cause the problem.

 

Example:

In my example I have a Patient Referral sharepoint list that I will add a new patient/create new item whenever I get a phone call. When a new patient is added, I have to select what clinic I referred them to. I use the "AssignedToClinic" lookup column to select the clinic that is in the source ClinicList. This will get all of the details of the clinic and pull it into my patient referral list. My flow is triggered whenever a new item is created in the Patient Referral list.

 

Source of Lookup Column - Clinic List

I created a SharePoint list called ClinicList. This basically shows clinics and the managing people. This list will be the source used by the lookup column in the second list.

Lookup Source Clinic List - The Clinic List is basically flat text values that will be the source of the lookup in the second list.Lookup Source Clinic List - The Clinic List is basically flat text values that will be the source of the lookup in the second list.Lookup Source Clinic List - List Settings and Column TypesLookup Source Clinic List - List Settings and Column Types

 

Main List Used for Flow - Patient Referral

The second list will be the one used by people to trigger flows and everything.

Main Action List Patient Referral - This is used by people and will have the lookup column that references the first ClinicListMain Action List Patient Referral - This is used by people and will have the lookup column that references the first ClinicListMain Action List Patient Referral - List Settings Column TypesMain Action List Patient Referral - List Settings Column Types

 

The Patient Referral list appears to have 7 Lookup type columns. But really I only added 1 Lookup column "AssignedToClinic" to the list. This is the primary lookup column where I will select the clinic. The secondary lookup columns are automatically applied because I checked the Show Additional Fields in the column settings.

The Lookup column AssignedToClinic will be the primary selection in the Patient Referral list, but additional fields are linked to this columnThe Lookup column AssignedToClinic will be the primary selection in the Patient Referral list, but additional fields are linked to this column

 

So when I create a new item in the Patient Referral list, I have to select the AssignedToClinic in the dropdown for the lookup. None of the other columns are edited when a new item is created.

But when I create the new item, all of the secondary linked lookup columns are filled in automatically.

Patient Referral List - Create a new item only requires selecting the AssignedToClinic lookup value.Patient Referral List - Create a new item only requires selecting the AssignedToClinic lookup value.When the new item is created all of the secondary columns are automatically filledWhen the new item is created all of the secondary columns are automatically filled

 

My basic flow is triggered when a new item is created in the Patient Referral list. This will show the separate value types that can be returned from the lookup column. My example only shows the AssignedToClinic dynamic content, but the results will be the same if I used any of the other lookup columns.

 

Dynamic Content Options:

AssignedToClinic Id - will be the ClinicList Item Id of the lookup value selected in the Patient Referral list

AssignedToClinic Value - will be the text string output of the lookup value

AssignedToClinic - will be the full object of the lookup value

 

There are 3 separate Dynamic Content options for each lookup fieldThere are 3 separate Dynamic Content options for each lookup fieldScroll through the dynamic content to see each of the optionsScroll through the dynamic content to see each of the optionsThe results of the flow show the outputs for each type of dynamic content optionThe results of the flow show the outputs for each type of dynamic content option

 

So please look this over and see if it helps you get the correct output. You want to select the dynamic content that ends with "Value" in order to get the single text output.

 

If you are getting different results than my example please let me know where you see the differences in column types or what is in your flow.

Will do in a bit!! Thank you!!

Thank you wskinnermctc! I did a separate lists/flow/test and it gave me the same results as yours. 

 

I just saved yours for future references along with your other instructions from previous posts.

 

EmailJoinIssue15.pngEmailJoinIssue16.pngEmailJoinIssue17.pngEmailJoinIssue18.png

 

From the flow that was giving me grief, my CTO, director, and myself managed to get it moving due to time constraints. We also ran into a silly Teams issue whereas we ended up having to split the teams into two or three (depending on which email status) and send it to EACH required person 😤 Outlook and Approval were fine with multiple people in one.

 

EmailJoinIssue12.pngEmailJoinIssue13.pngEmailJoinIssue14.png

 

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!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

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   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

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.    

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

Users online (1,681)