Answered

Triggering Power Automate to PowerApps Portal

Like (0) Share

Report

Posted on 3 Jul 2020 10:02:29 by Community Power Pla...

Hi all,

I am trying to connect Power Apps Portal to trigger Power Automate flow. I have this data from CDS with the following fields:

Unfortunately, I am not getting the desire output which should contains all its respected field. For Example:(Patient Name: Shane, Age: 25 etc).

Can someone please help me on this?How should i solve this problem?

Regards,

Ahmad.

I have the same question (0)

Summarized by AI

AI generated content may be incorrect

Did you find this summary helpful?

All responses (10)

Answers (2)

Verified answer

Joel CustomerEffective 3,224 on 08 Jul 2020 at 13:45:04

Like (0)

Report

Re: Triggering Power Automate to PowerApps Portal

sure, to get the label you need to do an expression like items('_<name of apply action>')['<name of the field>_label']

see https://crmaddicted.blogspot.com/2020/01/working-with-optionset-lables-in-power.html

If my answers helped you solve your problem, please mark as a solution.

Was this reply helpful? Yes No
Community Power Pla... on 08 Jul 2020 at 12:32:49

Like (0)

Report

Re: Triggering Power Automate to PowerApps Portal

Yes, solved.

I also have option set contains Male/Female which results in some integer numbers:

Can you please guide me on this?

Regards,
Ahmad.

Was this reply helpful? Yes No
Verified answer

Joel CustomerEffective 3,224 on 08 Jul 2020 at 12:15:33

Like (0)

Report

Re: Triggering Power Automate to PowerApps Portal

Your cropped photos don't give enough information and you haven't posted a screenshot of the edit mode of that step.

The newest screenshot shows you are passing a GUID, but it doesn't exist in the entity that you are looking it up in. Chances are you are sending the ID to the wrong entity. Check in CDS or a model driven app--can you open a record with that GUID in the entity to which you are doing the get record? open one of the records in that entity and change the ID= to the ID you are trying to pass it--if it is a real record in that entity you should be able to open it--if it isn't, you are likely choosing the wrong entity in your flow get records step.

what is the field you are passing to kaispe schedulers? Look at the definition of that lookup field--what is the target of the lookup field? That is the entity for which you should be doing your get record step.

Was this reply helpful? Yes No
Community Power Pla... on 08 Jul 2020 at 11:55:54

Like (0)

Report

Re: Triggering Power Automate to PowerApps Portal

Thank you again for your response jlindstrom.

Problem is, I also have tired this method but still facing an error:

Kindly please help me on this as i am stuck on this issue.

Regards,
Ahmad

Was this reply helpful? Yes No
Joel CustomerEffective 3,224 on 08 Jul 2020 at 11:44:18

Like (0)

Report

Re: Triggering Power Automate to PowerApps Portal

based on that error, either the item doesn't have a value or you put the wrong field reference in the get record step.

Get record is like a lookup--you choose the entity (where to find the value) and the record id, and it gets the entire record.

So in your original screenshot, you have fd5a7dcf-5bbc........ for the Doctor Name. That is the global unique identifier (GUID) for the Doctor . Assuming doctor is contacts you would do

Get record for contact and specify the Doctor name field for the identifier. This will then get the doctor record based on that ID.

Your latest screenshot doesn't show the definition of what you are passing to the get record step. The error makes me think the value of the field you are passing is KSP-1, which is not a GUID, so you likely have selected the wrong field reference for the identifier for the get records step.

also, be sure to rename your steps, especially get record steps. It gets really confusing if you don't.

Was this reply helpful? Yes No
Community Power Pla... on 08 Jul 2020 at 05:21:47

Like (0)

Report

Re: Triggering Power Automate to PowerApps Portal

Thank you jlindstrom for your effort, i really appreciate it.

As i am following your steps to input the my record id as an unique identifier to get record like this, i am facing the following error:

I am also confused about item identifier in get record action and then followed this thread: https://powerusers.microsoft.com/t5/Building-Flows/Dynamics-365-get-lookup-field-text-in-Power-Automate-Create-step/td-p/487193 . I am trying to give my unique id of the record which throws an error.

Is there any way better way to solve this issue?

Thanks in advance.

Regards,
Ahmad.

Was this reply helpful? Yes No
Joel CustomerEffective 3,224 on 03 Jul 2020 at 14:44:56

Like (0)

Report

Re: Triggering Power Automate to PowerApps Portal

@Anonymous I made a video showing how this works https://youtu.be/jrGpuG3Ambg

Was this reply helpful? Yes No
Joel CustomerEffective 3,224 on 03 Jul 2020 at 14:15:36

Like (0)

Report

Re: Triggering Power Automate to PowerApps Portal

@Anonymous --that is the GUID for these related records. Do a get record step for each one and refer to the name from each step.

Was this reply helpful? Yes No
Community Power Pla... on 03 Jul 2020 at 10:46:59

Like (0)

Report

Re: Triggering Power Automate to PowerApps Portal

Thank you jlindstrom for your response.

I am giving an input record id to Item identifier. Unfortunately i am getting this same issue above in a get record action:

In the output section I have three lookup fields and one option set contains some type of id which is not a problem in text fields.
Same thing happens above when i simply triggered when a record is created.

Is there a way to solve this problem?

Regards,
Ahmad

Was this reply helpful? Yes No
Joel CustomerEffective 3,224 on 03 Jul 2020 at 10:08:50

Like (0)

Report

Re: Triggering Power Automate to PowerApps Portal

Yes—add a get records step after the when a record is created. On create or update steps don’t return all of the fields, especially lookup fields and fields that are null. So after the trigger do a get record step based on the Id of the record in the trigger

Was this reply helpful? Yes No