Skip to main content
abdulrahimb9853
abdulrahimb9853
September 9, 2025
Solved

How to trigger a record action using a!buttonWidget instead of a!recordActionField

  • September 9, 2025
  • 5 replies
  • 0 views

I want to create a custom UI where all my actions are displayed as styled buttons using a!buttonWidget, but still open the native record action dialog (start form, etc.) the way a!recordActionField does. Currently, a!recordActionField works fine for triggering the action and opening the dialog, but it doesn’t give me the same level of styling flexibility as a!buttonWidget. I tried using a!startProcess() inside the saveInto of a button, but that just runs the process silently without opening the dialog. Is there any way to call a record action directly from a button widget (and open its dialog), or is a!recordActionField the only supported method?

Best answer by shubhama926776

You cannot directly trigger a record action dialog from a!buttonWidget.
a!recordActionField is currently the only supported way to trigger record actions with their native dialog behavior.
There's no function or method to invoke a record action dialog from a button's saveInto.
I would recommend, Use a!recordActionField with its built-in styling parameters and wrap it strategically.

5 replies

shubhama926776
shubhama926776Answer
September 9, 2025

You cannot directly trigger a record action dialog from a!buttonWidget.
a!recordActionField is currently the only supported way to trigger record actions with their native dialog behavior.
There's no function or method to invoke a record action dialog from a button's saveInto.
I would recommend, Use a!recordActionField with its built-in styling parameters and wrap it strategically.

    abdulrahimb9853
    abdulrahimb9853Author
    September 9, 2025

    Thanks a lot for clarifying this [emoticon:4baf9c67c1b843c6b4ddedea33023652], that makes sense. I noticed though that the other button in the same interface is actually using a button widget, so I’ll need to align the approach for consistency.

    stefanhelzle0001
    stefanhelzle0001
    September 9, 2025

    Use the record action field. In case you need all buttons to be primary, use a list of record actions field instead of a single field with multiple actions.

    harshas2775
    harshas2775
    September 9, 2025
    is a!recordActionField the only supported method

    If you have to have dialogs then Yes! Record action field is the only supported method. 

    If design without Dialog is acceptable then you can style a card as a button and use a!startProcessLink() in it to show initial chained UITs. You will also need to use layouts like column/side by side to have good UX design for different components. 

      Terms & ConditionsAccessibility statement