CDS: Is there a better way to map data that has a Lookup Entity?

[Reylin]

I'm using a flow to create word documents containing data from a CDS entity. 

Normally I would use Select and do it easily like this screenshot example: 

but the "site" field is a Lookup entity, and therefore the dynamic content coming from the CDS flow action is only the GUID. I do not get the Name (primary field), only the GUID. So I can't map it with the dynamic content. 
The solution I found is a nested loop with a condition like this: 

but loops with conditions take time... nested loops take exponentially longer. I dread using this solution as it will make this flow's runtime extend from a few seconds to several minutes long.

Is there any way I can dynamically add the Site name from the lookup entity into the Select action? 
Like filter/switch code I could put into the mapping value... 
It seems like such a small thing that I need such a huge mess of a flow for. 

[Jcook · Accepted solution]

Hello @Reylin

Check out my blog to bypass the apply to each loop when getting a CDS value from lookup using list records:
https://powerusers.microsoft.com/t5/Power-Automate-Community-Blog/Bypass-Apply-to-each-loop-on-singl...

—Josh
If you like my post please hit the "Thumbs Up" -- If my post solved your issue please "Mark as a Solution" to help others

[Reylin]

Thank you so much!