Hi all! Question on the behavior of bulk edit. Cur...
# troubleshoot
m
Hi all! Question on the behavior of bulk edit. Currently if someone selects 1000 datasets of which they own 999, but one they don't (accidental selection) the bulk edit will fail for all 999 along with the 1 they don't have access. My question, is that the desired behavior or a possible issue with the current solution? Appreciate feedback (and as applicable clarification) on this question. Thanks!
e
Hey @miniature-eve-21984 is this bulk editing on the UI?
m
Yes
b
Yes that is the intended solution!
The alternative is to have a set of mixed entities, some of which were changed as intended and others which were not
For the sake of reducing confusion, we've decided to make bulk edits an "all or nothing" thing
Otherwise as you can imagine it could get very confusing, where users think that actions were applied to all selected entities, but maybe a subset did not work! This can lead to issues later down the road if you've assumed that the action worked 🙂
m
Thanks @big-carpet-38439!
@big-carpet-38439 - follow up question, would the team support a specific error message for the above scenarios to aid in the data steward understanding why the bulk edit failed beyond the generic failure message? Asking to understand if we should look to contribute back or not if we think we need this level of details for our customer base. Thanks!
b
Yes i think we should 100% improve the error messaging where its insufficient 🙂
m
@nice-window-93693, @rhythmic-agent-54913 FYI.. can we have the team contribute back a more descriptive error message for bulk edit UI error driven by no authorization (see above thread details). Sounds like @big-carpet-38439 and team are good with such a contribution back. Cheers!
e
That would be fantastic, thank you!
b
Absolutely! Please let us know what we should review 🙂