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

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Invalid argument type ...
Power Apps
Answered

Invalid argument type (Text). Expecting a Record value instead.

(1) ShareShare
ReportReport
Posted on by 301
I have an app that triggers a flow from a button. My flow inputs are Text from the Power App. By default, all the inputs are required and the call from my OnSelect works, and it looks like this...
MyFLow.Run(TitleValue.Text, DescriptionValue.Text, NotesValue.Text)
The requirements changed and the NotesValue no longer needs to be required. I change this in my flow inputs, from the ellipsis on my input variable ("Make this field optional"), now my call from my button is giving me an error on NotesValue. The error is "Invalid argument type (Text). Expecting a Record value instead.
If I change the NotesValue back to being required, the error goes away. Why am I getting this error? What am I missing? 
 
 
Update with screenshots:
this is how I am running the flow from my Button.OnSelect
 
and this is how I updated the change to make NotesValue not required, from the trigger within myFlow
 
When I make the change, I see it as giving me the option to now make it required...which tells me it is now optional
 
With this change to make the last input optional, I save and refresh myFlow in Power Apps, and get this
 
Categories:
I have the same question (0)
  • Suggested answer
    Michael E. Gernaey Profile Picture
    53,433 Super User 2025 Season 2 on at
    Hi
     
    Did you remember to refresh your flow, in the app?
     
    Otherwise I got nothing as the error doesn't make sense, based on what you said you did. We cannot verify as we dont see the flow, the trigger, or know how you changed it.
     
  • Spawn10 Profile Picture
    301 on at
    @FLMike ,
    Thanks for the response. I have updated the post with the screenshots. Hopefully they help with reproducing the issue. 
  • Verified answer
    Spawn10 Profile Picture
    301 on at
    This was the workaround I came up with. I reverted the input in the flow back to being required, then changed the logic in OnSelect to...
    This got rid of my error, and the flow is being triggered. Willing to discover a more efficient way, if there is one. 

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

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 739 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 343 Super User 2025 Season 2

#3
Power Platform 1919 Profile Picture

Power Platform 1919 268

Last 30 days Overall leaderboard