Coming Soon: Updated Bulk Edit Feature

General Overview

The new bulk edit feature will provide a way to:

bulk edit a reading view
for multiple assets
across a range of dates

Here are the details of how it will work, along with any limitations and recommended best practices:

Set up:

If any attribute in a reading view is marked as bulk editable, that reading view is considered for bulk edit

General Recommendations

If any one attribute in the reading view is made bulk editable, all required attributes will be selected for bulk edit. For bulk update readings use case, if users don’t want to update required fields then they can deselect attributes from bulk edit flow.
If 2-3 attributes collectively contribute to the validation formula behavior or the calculation formula behavior and any one among them is needed for bulk edit then the whole group should be selected for bulk edit.

General Flow

Select the reading view
Select the date range - the date range allowed to select will honour the limitations of edit restriction specific to reading view
Enter values for the attributes
Select assets
Do bulk edit
If readings already exist user gets the option to retain/overwrite readings for those assets
Readings are auto-created or updated depending upon if any reading is already present and if user is selecting retain or overwrite.
Ineligible events or ticket readings creation/updation will be skipped and users will be notified with the list of assets after bulk edit completion.

General Limitations:

If a reading does not have a required field that is enabled for bulk edit, it will not be bulk editable in the app

#	Reading Type	Type	Multiple per day	How it works	Limitations	Recommended Best Practice
1	Core Workspace (e.g. Well, Tank)	Bulk Create	Yes	Creation will happen for assets which do not have any reading in that date. CF will be considered only for the latest reading by reading date If any ineligible readings are created through bulk edit then it can be fixed via exception flow	If user bulk creates/edits a tank reading on Dec 1,2,3 with open/close gauges - then the CF will only occur from Dec 3rd onwards as Dec 1,2,3 are manually forced to a value.	NOTE that while the setup is possible, it is not advisable to perform multi date range bulk edits on tank gauges due to the limitations noted. Bulk edits on tank gauges, if needed should be done for a single date only. This should be handled by training if needed. Suggest training users to only perform date range updates on comments
2	Core Workspace (e.g. Well, Tank)	Bulk Update	Yes	Update will happen for assets with reading already present for the date. If multiple readings exist in the day. All readings will be bulk updated. CF will be considered only for the latest reading by reading date and reading time If any ineligible readings created through bulk edit then it can be fixed via exception flow	If user bulk creates/edits a tank reading on Dec 1,2,3 with open/close gauges - then the CF will only occur from Dec 3rd onwards as Dec 1,2,3 are manually forced to a value.	NOTE that while the setup is possible, it is not advisable to perform multi date range bulk edits on tank gauges due to the limitations noted. Bulk edits on tank gauges, if needed should be done for a single date only. This should be handled by training if needed. Suggest training users to only perform date range updates on comments
3	Core Workspace (e.g. Well, Tank)	Bulk Create	No	Same as #1
4	Core Workspace (e.g. Well, Tank)	Bulk Update	No	Same as #2, except that there will be single record per day
5	Core Ticket	Bulk Create	Yes	Ticket creation is not supported	N/a	N/a
6	Core Ticket	Bulk Update	Yes	Update will happen for assets where ticket is already present for the date. If multiple tickets exist in the day. All tickets will be bulk updated. If ticket reading for any asset becomes ineligible with bulk edit flow that reading will not be created/updated. User will be shown the list of assets in the end for which readings creation/updation were skipped. Core workspace will be updated for respective dates If reading is not present in core ticket, No new ticket will be created	Exception flow for tickets not handled as bulk edit won’t allow to create ineligible readings	Suggest only making “Comments” field bulk updatable
7	Custom Event	Bulk Create	Yes	Creation will happen for assets which do not have any reading in that date. If event reading for any asset becomes ineligible with bulk edit flow that reading will not be created/updated. User will be shown the list of assets in the end for which readings creation/updation were skipped. If workspace is dependent on event, workspace will be updated If workspace reading is not present it gets created CF for workspace will be considered only the latest reading by reading date	Exception flow for Events not handled as bulk edit won’t allow to create ineligible readings
8	Custom Event	Bulk Update	Yes	Update will happen for assets where readings are already present for the date. If multiple events exist in a day, all events will be updated If event reading for any asset becomes ineligible with bulk edit flow that reading will not be created/updated. User will be shown the list of assets in the end for which readings creation/updation were skipped. If workspace is dependent on event, workspace will be updated If workspace reading is not present for any date it gets created CF for workspace will be considered only the latest reading by reading date	Exception flow for Events not handled as bulk edit won’t allow to create ineligible readings
9	Custom Event	Bulk Create	No	Same as # 7	Exception flow for Events not handled as bulk edit won’t allow to create ineligible readings
10	Custom Event	Bulk Update	No	Same as #8, except that there will be single record per day	Exception flow for Events not handled as bulk edit won’t allow to create ineligible readings