Answered

Text Input - OnSelect Property

(0) Share

Report

Posted on by JLam63

Hi everyone, so I recently have been looking into PowerApps. Just wondering on the Text Input control, I was looking into OnSelect property (all I know so far for OnSelect is Navigate), I tried to use Navigate and when I ran it, it did nothing. Of course when you click into the field it will let you input text, if I click on the edges of the control it just does nothing. Thanks in advance

Categories:

Building Power Apps

All responses (4)

Answers (1)

Sort by

Sienna 1,532 on at

Like
a
(0)

Report
Copy link

Link copied!

I'm not sure why you want to navigate on onselet of text input but if it does't work then you probably have your code wrong

Navigate(Screen2,ScreenTransition.None)

That how it should be done

Here you can find more function you can use in onselect properties. I would suggest you to go through each one and play with it before you start on your app

https://docs.microsoft.com/en-us/powerapps/formula-reference
JLam63 48 on at

Like
a
(0)

Report
Copy link

Link copied!

I have written the code correctly, as to why I am trying this, well I'm justing testing out PowerApps and all it's functionality and seeing what it can and cannot do. Would I myself do something like this in an app? Not in a situation I can currently think of but you would never know.
Verified answer

v-monli-msft Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @JLam63,

I just tested and I cannot reproduce your issue.

1. Insert a TextInput1 control, and set its OnSelect property to

Navigate(Screen2,ScreenTransition.None)

2. After this, when I select any part(including content part) of this TextInput1 control, it will navigate to Screen2 immediately.

Regards,

Mona
JLam63 48 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

I just created a new Text Input Control and tried it again, it is working now.. don't know what happened yesterday, I know I had the correct code and I also had someone look over it. Might've been something we both missed somehow or something else making it not work. Either way it is working now, thanks all for helping and testing this out.