web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Finance 'Get a Record'...
Power Automate
Unanswered

Finance 'Get a Record' asking for two key values but only provides one input box

(0) ShareShare
ReportReport
Posted on by J-G 134

I'm attempting to do some testing with data from a Finance application, but for some reason the flow action for getting a record is saying that I need to provide the values for two keys for lookup, not just the item id (no clue why this would be a requirement). However, there's only one input in the action, and I don't know how to format a multi-key lookup. 

 

JG_0-1715691489986.png

 

(I deleted all the values for security reasons; when filled in, there's still only one box for Object Id).

 

JG_1-1715691531569.png

The actual error message itself (I left the key columns out of the screenshot). 

Categories:
Using flows
  • JPJohnson Profile Picture
    JPJohnson 4 on at

    I experienced the same thing and solved it today. The entity I was trying to get a record from had two keys. The legal entity and the purchase order number. We added both and it kept failing. So eventually we added a comma between the two keys and made sure it was placed in the correct order (Legal entity and then purchase order) and it worked. If we had them in a different order (PO then Legal Entity) it did not work, and if we removed the comma it did not work. Good luck and I hope this helps! 🙂 

  • J-G Profile Picture
    J-G 134 on at

    Yeah, that's what we figured out as well. Unfortunately, after that we ran into the issue of the action absolutely insisting we had to provide a value to update a field with despite it being read only, thus preventing the action from ever being accomplished. I have no clue why an update action would have required fields when logically any record created would have to go through the non-nullable field rules set up for the model, but that's the way Microsoft designed it I guess.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Mohsin Ali Profile Picture

Mohsin Ali 430

#2
11manish Profile Picture

11manish 341 Super User 2026 Season 2

#3
M Bilal Khan Profile Picture

M Bilal Khan 282

Last 30 days Overall leaderboard

Featured topics

Known issue with browser automation in Power Automate for Desktop on Google Chrome 146 and 147
Share your ideas and struggles with building Power Automate flows!
Survey: Power Automate mobile app
How to Ask for Help with Your Power Automate Workflow
Start and wait for an approval action
Restore a deleted flow
List of actions cheat sheet for Power Automate Desktop
Welcome to the Power Automate forum!

Product updates

Microsoft Power Platform Community release plans