Designing a new feature: bulk changes

For one of our next Sprints, we plan to implement a bulk change function for objects. I described our first idea of that function in the following issue:

Sometimes a user needs to update multiple objects at once. For example, for a set of routers, a specific location needs to be set. At the moment, the user needs to update every router object one by one or export all routers as CSV, updates them in Excel and re-import them. For that reason we need a better support for bulk changes.

functionality
In the object table (which list all objects of a specific type), the user should select all items, which he wants to change. The filter functionality of the object table should support him, to find the correct objects.

After selecting the objects in the object table, the user should click on a “bulk change“ button, which brings him to an empty edit page. On this page, an empty edit view of that object type should be shown. On this page, the user can set values for fields he wants to change. Each field he wants to change should be marked with a checkbox. On a click on “save”, for all selected objects, the marked fields should be set to the new value. All other fields of the selected objects should not be changed.

You are welcome to share your thoughts and comments about our idea.

Hi,

the basic idea is nice and this feature is without doubt a must have.

I’d like to see some sort of Feedback when editing a large amount of data more or less destructively.
The “edit form” could be prefilled with a representation of the data you are supposed to edit.
e.G.:

  • this field is empty in all selected datasets -> empty field
  • there is the same fiel value in all selected sets -> show value
  • there are different values in all selected sets -> print somethings like “multiple” or so (ok, we should think about checkboxes here too :slight_smile: )
    There also could be a label that says “changes affecting 4 rows” … or something like that.

After editing a preview of all data that you are going to edit could be helpful, just for a final sanity check and confirmation before finally executing all changes.

1 Like

Hi Michael
Pls. think also about some Security features like having a possibility to define during definition of a field to allow a bulk update of this field. (I think about IP address). There are fields where it make sence to bulkupdate but also where not.!

I thought about a 4 eye’s principle to allow or disallow bulk Update?
Maybe It is needed to have the choice while defining a field eg.
-> Bulk updateable (yes, no, 4-eyes)

Kind regards
Joachim

1 Like

Hi to all,

and thanks for all your feedback. We reviewed the planed bulk change function and updated our Jira Issue:

  • [NET-275] Bulk changes of objects

Sometimes a user needs to update multiple objects at once. For example, for a set of routers, a specific location needs to be set. At the moment, the user needs to update every router object one by one or export all routers as CSV, updates them in Excel and re-import them. For that reason we need a better support for bulk changes.

functionality
In the object table (which list all objects of a specific type), the user should select all items, which he wants to change. The filter functionality of the object table should support him, to find the correct objects.

After selecting the objects in the object table, the user should click on a “bulk change“ button, which brings him to a new page.

On this page, an empty edit view of that object type should be shown. Each field of the object type should be shown with a little checkbox beside the field. This checkbox will mark the fields, that should be changed within a bulk change. If a user change the content of a specific field, the checkbox beside the field should be set to marked. On this page, we also provide a preview button, which opens a preview of the changes in a popover. This preview should show a table with all selected objects (pagination) with the following columns:

  • public ID
  • object summary
  • changes
  • with each changed field producing a line with old value → new value

On a click on “save”, for all selected objects, the marked fields should be set to the new value. All other fields of the selected objects should not be changed.

In short: we added a preview function of the bulk changes.

Also, the Four-Eyes principle was a nice idea, for which I created a Jira task in our backlog (NET-372). We also plan a function to ensure, that the content of a field is unique (NET-334). For such fields, we should disable bulk changes in the future.

Thanks again for your feedback. We plan to implement bulk changes in our next Sprint and to include this feature in version 1.2.0 (which will be released 29th May 2020).

Hi to all,

yesterday we finished the development of bulk changes and I want to share the first screenshots with you:

At first, choose the elements you want to change in the object table and click on the “Bulk change” button:

Edit the fields you want to change:

Review your changes before you save:

This function will be available in our 1.2.0 release at 29th May 2020. Thanks again for all your ideas.