bNewDocumentUpdate appears to only work for minor versions, not major.

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

bNewDocumentUpdate appears to only work for minor versions, not major. Is this a bug, or by design?

Categories:

Building flows

I have the same question (0)

All responses (12)

Answers (0)

Sort by

Expiscornovus 33,830 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @Anonymous,

As far as I am aware it just increments one version. So, if you have minor versions enabled it will go from 1.0 to 1.1. If you just have major versions enabled it will go from 1.0 to 2.0.

Below is an example

1. Same request for different libraries

2. Minor versions result

3. Major versions result

So, it really depends or your versioning setup.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi, sorry, my question was a little too vague...
We're having a problem when you set bNewDocumentUpdate to true that it should update the row without incrementing the version and that's what doesn't seem to work on major versions.
When bNewDocumentUpdate is set to false then it increments the version as expected.

Was this reply helpful? Yes No
Snoemannen 32 on at

Like (0)

Report
Copy link

Link copied!

It doesn seem to be working when having bNewDocumentUpdate set to true so the versions does not increment when updationg.
For minor versions it works but when the document is on a major version SharePoint seems to be throwing a weird error.

Was this reply helpful? Yes No
Expiscornovus 33,830 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @Anonymous,

Thanks for the clarification. It should also work with the true value as well.

Do you get any specific error? If so, please share that error? And can you also share the Body payload you are using in the HTTP request for the major version one.

Below are my tests with the true value.

1. Same request for different libraries

2. Minor versions result

3. Major versions result

Was this reply helpful? Yes No
Snoemannen 32 on at

Like (0)

Report
Copy link

Link copied!

Does your library with major versions also have minor versions?
If you publish the file in the library with minor versions and then try again when the file is on a major version, does it still work?

For us when the file is on a minor version it works as it should:
and the version was 2.28 befor as well:
But if I then publish that file so the version is 3.0 and try again with:
Then I get an error from the api withe the cryptic error message
"Additions to this Web site have been blocked.\n\nPlease contact the administrator to resolve this problem"

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@Expiscornovus - do you have any further input to the question/scenario that @Snoemannen posted?

Was this reply helpful? Yes No
Expiscornovus 33,830 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @Anonymous,

I used two different libraries (one with minor versions and one with major versions) in my test. So, I tested both scenarios and both scenarios should work (at least they did in my dev environment). So, I am unable to reproduce your issue.

Might be related to other parts of your setup. I see you are using MMS type of columns. Also worth knowing your libraries settings. Do you for example also use Content approval in the library and/or Check-in/Check-out, etc.

The error 'Additions to this website have been blocked' suggest that the site might be in a lock state? Can you double check that as well (may be you have reached a storage quota limit for this site?).

Was this reply helpful? Yes No
Snoemannen 32 on at

Like (0)

Report
Copy link

Link copied!

It is neither of those scenarios.
It is not in a library that only allows major version but in a library with both major and minor versions but the file is published to a major version.
Then the request fails.
I start to believe it is by design somehow since if I recall correctly it is the same problem if you use the standard action in power automat to check in a file, there you have the option to create a minor version, create a major version or overwrite the current version and if you choose overwrite on a file that is already published to a major version it fails as well.

Was this reply helpful? Yes No
Expiscornovus 33,830 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hi @Snoemannen,

Are you a colleague of @Anonymous? It is a bit confusing to discuss this with two people at the same time, lol 😂

Might be a miscommunication from my part. In earlier replies I called one of my tests minor versions but I obviously meant the Create major and minor (draft) versions option in the document version history settings. There isn't a minor versions option available in the document version history settings.

So, I also tested that scenario as well, sorry for the confusion. In the screenshot below that is Test B (bNewDocumentUpdate false). As you can see it didn't have an issue to update the version of the Doc from 1.0 to 1.1. That's why I believe there is some other thing going on in your situation/setup.

To get to the bottom of this I would need a bit more information. Did you see my earlier questions, it would still help troubleshooting to get an answer on those:

- Have you checked the lock state of the site? It would be good to double check if the site is not locked at the moment.

- Can you share the library settings and also the columns? This way I can try to reproduce this and try to find the root cause of your issue.

Edit: added the two other tests as well. Since I tested four scenarios.

bNewDocumentUpdate true

bNewDocumentUpdate false

Was this reply helpful? Yes No
Snoemannen 32 on at

Like (0)

Report
Copy link

Link copied!

Yes we are colleagues 🙂

Not at the computer at the moment but try this:
Have minor versions enabled on the library.
Publish the file to a major version, for example 1.0
Have bNewDocumentUpdate set to true so it tries to do an update without increasing version, then it fails.
If it is on a minor version as in your example then it does work.

Was this reply helpful? Yes No