Hello @johnjohn123
https://powerapps.microsoft.com/en-us/blog/enhanced-component-properties/
As the page above indicates, Microsoft has renamed 'behavior' properties' to 'Events.'
(I believe that an experimental phase is a step in the process leading to the General Availability (GA) and The likelihood of deprecating the feature is low because It is a core feature for creating components.)
The YouTube tip you mentioned seems to offer limited options, displaying only 'OK' and 'Cancel.' (Of course, using a popup with 2 buttons could be enough for many occasions). However, there could be more options that a user might need to select, depending on the context of the screen, such as 'OK/Cancel/Confirm/Skip/Print/Approve/Return/Delete/Restore/...Many other actions....' Instead of directly defining the types of buttons that a user can choose within the component, it would be more practical to allow the component to accommodate all possible choices you design.
In my case, I typically add properties to distinguish each action. An example is...
SelectedAction is used to distinguish each action performed by each button you create on the pop up window.
when creating pop up window with 4 buttons.
UpdateContext(
{tblButtonsInfo: //define buttons for screen, button options are different depending on a screen
Table( //Pop Up window component uses below properties to populate buttons, "Do Action1", "2", "3"....and "Cancel"
{
Name: "Do Action1", //This is just a text to be displayed on the button.
Action: "ACTION_COMMAND_1", //I use a constant style to distinguish each type and avoid conflicts in cases where 'Name's are duplicated.
Order: 1,
Other properties for look & feel
},
{
Name: "Do Action2",
Action: "ACTION_COMMAND_2",
Order: 2,
Other properties for look & feel
},
{
Name: "Do Action3",
Action: "ACTION_COMMAND_3",
Order: 3,
Other properties for look & feel
},
.................
{
Name: "Cancel",
Action: "CLOSE_WINDOW",
Order: N,
Other properties for look & feel
}
)
}
);
Inside the OnSelect property of the component you created(Added) from the custom component.
Switch(SelectedAction, //Check the hidden constant behind the button that a user clicked.
"ACTION_COMMAND_1", Action that you want,
"ACTION_COMMAND_2", Action that you want,
"ACTION_COMMAND_3", Action that you want,
"CLOSEW_WINDOW", UpdateContext({blnShowDlg :false} );
I hope this helps. (If this is not what you were asking, I seek your understanding)
