Are you suggesting that each button will have its own ConfirmDialogProvider?
I was assuming that the same ConfirmDialogProvider can be used for all the buttons.
The dcc.ConfirmDialogProvider can have multiple buttons as children (in a list), but based on the properties of the dcc.ConfirmDialogProvider, I think you canโt extract the information concerning which of the children actually triggered the dialog.
If your intention is to start a different process depending on which button has been clicked, you need the information of the triggering button. Hence the need for wrapping each button in a separate dcc.ConfirmDialogProvider IMHO.
I got the wrapper function logic. Even if I do so!
I donโt see the callback function that asks for confirmation from the user for the relative button clicked.
Also seems like the callback_context.triggered_id is depreciated. Somehow the dialog box is not poping with the example given.
The problem was at my side all my buttons were under dbc. group button and hence escaping the wrapper function logic. I think you can ignore my last query