-
Notifications
You must be signed in to change notification settings - Fork 411
Closed
Closed
Copy link
Labels
status:fixed-next-dropIssue will be fixed in upcoming release.Issue will be fixed in upcoming release.
Milestone
Description
Category
[ ] Enhancement
[X] Bug
[ ] Question
Version
Please specify what version of the library you are using: [3.20]
Expected / Desired Behavior / Question
When creating a document set using a dynamic form, this should just work.
Observed Behavior
For some tenants, and only sometimes, a 409 save conflict exception is thrown when submitting the form. It appears the folder is created still, but not updated to be a docset with all the filled in metadata.
The issue occurs on this line:
| const iur = await library.items.getById(folderId).update(objects); |
Steps to Reproduce
It's hard to reproduce unfortunately. My customer has it all the time (in two M365 tenants), but in my tenant I haven't seen the issue occur yet.
Fix
What we could do is add some intelligence to retry updating the list item based on the error that's returned.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
status:fixed-next-dropIssue will be fixed in upcoming release.Issue will be fixed in upcoming release.
