SetFocus does not work with Modern TextInput in Power Apps

Dear @NEV IT02,

Thank you for providing the detailed context. I can understand how these behaviors are affecting your input flow and overall user experience.

According to my research based on the current Power Apps behavior, what you are observing with SetFocus() is expected. The function cannot set focus on controls that are placed inside container controls, including Vertical Containers. For reference: SetFocus function

Regarding the TriggerOutput property, when it is set to Delayed, the platform applies a short internal delay before updating the control’s value or firing related logic. However, there isn't any official information about the supported way to configure or adjust this delay duration. For reference: Text Input modern control in canvas apps and Text input control in Power Apps

However, the issue you are facing is related to Microsoft Power Platform (specifically Power Apps), rather than Office 365 products. As this forum mainly focuses on Office 365 services, there may be limitations in the depth of support I can reliably provide for Power Platform-specific scenarios.

Therefore, to ensure that you receive the most accurate guidance, including recommended customizations and proven workarounds, I would strongly suggest posting your question on the Microsoft Power Platform Community. This forum is dedicated to Power Apps and related technologies, and it is actively monitored by product experts, engineers, and experienced community members. You can reach out to a highly specialized audience who deal with similar scenarios regularly and can provide more targeted solutions. It is also a great place to learn from existing discussions and shared best practices.

You can access it here: https://community.powerplatform.com/

Note: I truly apologize for redirecting you to a different community as the members of the posted category focus on users with Microsoft 365 concern and have limited knowledge about Power Automate, so to get a quick and better assistance, I redirect you in the correct way. 

I appreciate your patience and understanding and thank you for your time and cooperation. If you have any further questions or any concerns, please feel free to reach out. I'm happy to assist further.

1. SetFocus and Vertical Containers The provided information only documents how SetFocus is used in general (for example, on a screen’s OnVisible to focus a control) and how focus can be driven indirectly via component InputEvent using a SetFocus-prefixed string. It does not document any limitation or behavioral difference for controls inside a Vertical Container versus outside it, nor does it distinguish between classic and modern TextInput for SetFocus. The behavior described (working outside but not inside a Vertical Container) is therefore not covered by the referenced documentation and cannot be confirmed as by-design or a regression from the available material.
2. Classic vs. Modern TextInput The context explicitly documents behavior differences for modern Text Input controls (for example, OnChange firing on focus out and the TriggerOutput options), but does not state any difference between classic and modern TextInput regarding SetFocus. No statement is provided that SetFocus is unsupported or behaves differently for modern TextInput compared to classic.
3. Customizing TriggerOutput.Delayed duration For modern Text Input, TriggerOutput supports:

• TriggerOutput.Keypress
• TriggerOutput.FocusOut
• TriggerOutput.Delayed

The documentation states that Delayed is used in forms for better performance but does not expose any property or setting to configure the delay interval. There is no documented way to customize the delay duration of TriggerOutput.Delayed for Text Input (classic or modern) in the provided material.

4. Workarounds (based on documented behavior) Within the documented capabilities:

• To react immediately to user input without relying on OnChange, formulas can reference the Text Input’s output property directly (for example, TextInput1.Text) while using TriggerOutput.Keypress when per-keystroke responsiveness is needed.
• For focus control in component scenarios, focus can be driven via an InputEvent pattern using a context variable whose value starts with "SetFocus" and changes each time, for example:

    UpdateContext({ ctxComponentEvent: "SetFocus" & Text(Rand()) });
  

  with the component’s InputEvent bound to ctxComponentEvent.

The documentation does not provide a specific workaround for SetFocus failing inside a Vertical Container, nor any container-specific focus guidance beyond the general SetFocus and InputEvent patterns.

References:

• SetFocus function
• Set Focus on a control
• Text Input modern control in canvas apps
• Recent updates to modern controls in canvas apps
• Modern controls and properties in canvas apps
• Text input control in Power Apps
• Isolate issues in canvas apps