Hi,
So I have created a flow to send notification to Teams whenever a record is created, reviewed, or completed. I have used an HTTP action to post depending on the status of the record.
I am having trouble with displaying lookup fields - I have two lookup fields of;
1. Developer - which looks up the user
2. Project - Which looks up the open projects. This is an option set.
The post I get in Teams does not display anything in front of projects, and gives a string of numbers and characters in front of Developer. How can I fix this?
Thank you
Solved! Go to Solution.
You haven't mentioned what's your data source is? Believe its D365 record you creating. To get the user name you need to use Get Record, pass the identifier (GUID) to retrieve the user name. For optionset you need to check the run history and see if you could see anything called yourfieldname_label. If it exists then use that dynamic property to display the option set name. If not you need another List Record action step looking against StringMaps entity then set the field name, entity name and option set value to get the option set name.
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blog
To retrieve the optionset label name you need to retrieve the stringmaps entity and set the relationship entity name, value and attribute name. Please follow the below link
https://himbap.com/blog/?p=3210
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blog
You haven't mentioned what's your data source is? Believe its D365 record you creating. To get the user name you need to use Get Record, pass the identifier (GUID) to retrieve the user name. For optionset you need to check the run history and see if you could see anything called yourfieldname_label. If it exists then use that dynamic property to display the option set name. If not you need another List Record action step looking against StringMaps entity then set the field name, entity name and option set value to get the option set name.
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogHi,
So this is what I did. Yet my result is still the same. Can you tell me what I am doing wrong.
Thanks for your reply. If your result still showing the same id that means you are mapping the wrong field. Check the run time history and make sure what values are returned from the Get record step. Also check the mappings are from Get record action step.
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogHey,
Thanks for the help.
So I have gotten the developer field to work. I looked up the results from the Get record and chose those dynamic fields in my HTTP post. That was First Name <space> Last Name.
Now, I am stuck on the option set post. So this field, i.e: Project, it looks up the records of an entity. I tried the List Record action step but I am a little lost after that. Can you help me with that please?
To retrieve the optionset label name you need to retrieve the stringmaps entity and set the relationship entity name, value and attribute name. Please follow the below link
https://himbap.com/blog/?p=3210
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogThese are the steps that I have followed. Helped with both my cases.
Thanks for the help. Appreciate it.
If you use the CDS connector you can get the label name directly from the Get record or items. Glad to hear that you have solved the problem and thanks for the confirmation.
Thanks
If you liked my response, please consider giving it a thumbs up
Proud to be a Flownaut!
Learn more from my blogLearn to digitize and optimize business processes and connect all your applications to share data in real time.
Read the latest about new experiences and capabilities in the Power Automate product blog.
If you are a small business ISV/Reseller, share your thoughts with our research team.
User | Count |
---|---|
25 | |
23 | |
9 | |
7 | |
6 |
User | Count |
---|---|
40 | |
35 | |
22 | |
20 | |
13 |