{"id":"687d7043bc44e0029186c03d","title":"2025 07 20","path":"how-to/committee/release-notes/2025-07-20","contentMarkdown":"#  20th July 2025 — [Add Bulk Edit on Event Data Management #42](https://github.com/nbarrett/ngx-ramblers/issues/42)\n## [build 186](https://github.com/nbarrett/ngx-ramblers/actions/runs/16389001373)\n- This requirement came about following some analysis of historic data on groups where the group name and/or code was not consistently populated across existing locally stored event data.\n- A Bulk Edit facility was added  on the Event Data Management (`/walks/admin/event-data-management`) page, to allow manual reallocation.\n- When the view is first visited and no events have yet been created the following alert is displayed:\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/f663b297-0d61-4168-a350-ec35099404c8.jpg)\n\n* However, once one or more imports have taken place (or your site has undergone manual input of walks), the view will appear similar to this:\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/44344a30-ea77-4855-a74c-b65971656bd8.jpg)\n\n## Bulk Deleting events\nTo be completed...\n\n## Bulk Updating events\nTo be completed...\n\n## Other changes within this release\n- The import help text was refined along with how parts of the import view are rendered during the import workflow.\n- Walk leader information on walks view and card were improved as there was a case when the leader was displayed twice if they had a display name but no phone number.\n- Fixed the walk leader api call which needed to be migrated from the old `/api/database/walks` endpoint.","contentHtml":"<h1>20th July 2025 — <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/42\">Add Bulk Edit on Event Data Management #42</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/16389001373\">build 186</a></h2>\n<ul>\n<li>This requirement came about following some analysis of historic data on groups where the group name and/or code was not consistently populated across existing locally stored event data.</li>\n<li>A Bulk Edit facility was added  on the Event Data Management (<code>/walks/admin/event-data-management</code>) page, to allow manual reallocation.</li>\n<li>When the view is first visited and no events have yet been created the following alert is displayed:</li>\n</ul>\n<p><img src=\"https://ngx-ramblers.org.uk/api/aws/s3/site-content/f663b297-0d61-4168-a350-ec35099404c8.jpg\" alt=\"\"></p>\n<ul>\n<li>However, once one or more imports have taken place (or your site has undergone manual input of walks), the view will appear similar to this:</li>\n</ul>\n<p><img src=\"https://ngx-ramblers.org.uk/api/aws/s3/site-content/44344a30-ea77-4855-a74c-b65971656bd8.jpg\" alt=\"\"></p>\n<h2>Bulk Deleting events</h2>\n<p>To be completed...</p>\n<h2>Bulk Updating events</h2>\n<p>To be completed...</p>\n<h2>Other changes within this release</h2>\n<ul>\n<li>The import help text was refined along with how parts of the import view are rendered during the import workflow.</li>\n<li>Walk leader information on walks view and card were improved as there was a case when the leader was displayed twice if they had a display name but no phone number.</li>\n<li>Fixed the walk leader api call which needed to be migrated from the old <code>/api/database/walks</code> endpoint.</li>\n</ul>\n"}