-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sap.m.upload.UploadSet aggregations do not get an update as uploadState property shifts #4027
Comments
Hello @cbsmerveguel , Thank you for sharing this finding. I've created an internal incident DINC0129133. The status of the issue will be updated here in GitHub. Best Regards, |
any update regarding #4029? |
The created incident: DINC0129133 is with the UploadSet Development team. In order to better process the issue would it be possible to provide us with an Application URL, where we can retest the similar behavior Or any location where we can test the above mentioned behavior? when we use insertItem or addItem API on the uploadSet control and pass the incomplete item to that method, it manages to remove it from incomplete list and place it in complete list. Please let us know if this was the expected outcome. Regards, |
Hi gurus,
We are using UploadSet with "incompleteItem" aggregation due to the fact that we are processing our uploaded documents first, and set them as "Complete" at a later point. As the processing gets finished, we set the incompleteItem's "uploadState" property as "sap.m.UploadState.Complete".
Our expectation was that as the "uploadState" property gets an update to "Complete", the "incompleteItems" and "items" aggregation would get an update too. The processed item gets reducted from the "incompleteItems" aggregation and added into the "items" aggregation. However, we got to see that it is not the case. The incompleteItem object stays in the "incompleteItems" aggregration, even if it has a uploadState of "Complete".
We tried to manually remove the item from the "incompleteItem" aggregation and add/insert it into the "items" aggregation but it didn't work, because the object id was already used and removed.
UI5 Version: sap.m.upload.UploadSet 1.120.8
We are asking your support and expertise on this matter,
*A follow-up incident of the main incident: #4026
Thanks in advance,
Best,
Merve
The text was updated successfully, but these errors were encountered: