I was working on the approval process of a SharePoint document. I did the following:

  • Check out the document
  • Make necessary changes to the document
  • Check-in the document as a Minor version (draft) 3.1
  • Submit for approval
  • Approved

Once approved, the version of the document changed to 4.0 instead of 3.1, means it published as a major version.

Is there any way that the published version still in the minor version?

Much appreciated for the suggestions and help.

  • When document is approved, next major version of document will be published. Do you want to continue using minor version instead of major version? Commented Sep 16, 2022 at 14:28
  • Yes, after the document is approved, need the document still in the minor version
    – Ullas
    Commented Sep 16, 2022 at 14:31

2 Answers 2


This cannot be done using SharePoint's built-in approval functionality. If you wanted something like this, you'd need to build something custom.

I haven't tried to do so but I think it could be done using Power Automate. The one issue that immediately comes to mind is, what happens when a user creates new minor versions while a previous minor version is awaiting approval? For example, what if an approver rejects 3.1 when the current minor version is 3.6?


As Rob said, this cannot be done as approved version (internal field name "_moderationstatus") imply version is majoir (.0).

What you can do is to manage a custom status field with choices Approved/Rejected and change by the means of a workflow task this custum status in Approved.

I did something similar for a customer, however this status is still for a draft version, and this imply all consequences of a draft (depending by library setting, draft version imght be not visible to other users)

Hope this help...

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.