How can we avoid that the users accidently use the standard publish-menu item and not the Flow-workflow I only know the SPFx approach for hiding the menu item but thats quite a huge effort.

Out-of-the-box SharePoint provides you with that functionality by selecting More Publish in the context menu of the file.

With that option, I can create a custom Flow button using column formatting (more on that later) and I can ask for comments (the same as you would be asked if you use the out-of-the-box Publish option in SharePoint).

I also want the file to be copied to another library after the file has been published, so lets go and jump into it.

We are asking for comments, so we can select the Text option and give it a name and a description.

If anything changes of if you want to use this Flow somewhere else you only have to change the variables and not each action by itself.

Please note that you do always need to specify the Site address and Library name in your For a selected item trigger.

Make sure you set the Site Address to our siteAddress variable and select the POST method.

The endpoint stated above needs to be configured in the Uri field.

Since we are using variables for our Get file properties action, we cannot select them as Dynamic Content so we must configure them manually by using the body() expression.

This window allows you to configure when the action should be ran.

To undo the check out, we need to do the same as the Check out action, only with a slightly different endpoint, which is.

Because we already added the undo check out option beneath our publish file action, we need to add a parallel branch to our undo check out option in which we add the Copy file action.

The internal name of this property is Identifier, so the body() expression for this property is.

Please note that this is both library name and (if applicable) subfolder(s).

We use the Path property for this in which we replace the source library name to the destination library name, using the replace() expression.

But this property expects its value without a trailing slash and the Path property always gives a trailing slash, so we need to remove that from our replace() result.

So if the length of the replaced Path was 11, it now will be 10.

Also make sure you put a forward slash in front of your expression.

We can do that by using column formatting to create a flow button.

Just select Add column in your library and put a space into the Name field and voila, theres your nameless column.

To enter your column formatting into your field, select the down arrow of the field, click Column settings and select Format this column.

The Format column pane will appear in which you need to paste the column formatting JSON.

I also tried to do something with the Version field (only show the button on minor versions), but since this is a system field, it cannot be used in your column formatting unfortunately.

Sharepoint Online Flow With Button