We are exploring deleting branch locations and consolidating them. Long story short, we set it up wrong and need want to move it to how it should be used.
We will probably wait until all open Service Orders / Appointments with the older branch locations are completed, closed & billed out until deleting them, but in a Sandbox I deleted the Branch Location and it makes that required field have a warning that the Branch Location has been deleted, and in the GI it is NULL.
What ramifications can I expect to see if I delete branch locations?
Best answer by rmillerKimball
@hdussa Oh, I didn’t check in the SQL that is great information! Thank you for that, this gives me much more confidence to move forward.
My plan for those venturing down this path in the future:
Create new consolidated Branch Location
Change all OPEN tickets with 0 items to the new Branch Location
Train dispatchers to only use the new Branch Location moving forward
Wait… After about 1 month, check all OPEN tickets with out new Branch Location and address these 1 by 1 (gross, I know).
After reconciliation of all OPEN tickets, delete old Branch Locations as available. Hopefully not going over 1.5 months after creating the new Branch Location.
I checked this in my local demo site for a completed Service Order. The Branch Location is still in the DB after I deleted it because the it was a soft delete. Like you noticed it shows a warning that record has been deleted and not visible on GI. I would simply execute SQL query to bring it back when required.
@hdussa Oh, I didn’t check in the SQL that is great information! Thank you for that, this gives me much more confidence to move forward.
My plan for those venturing down this path in the future:
Create new consolidated Branch Location
Change all OPEN tickets with 0 items to the new Branch Location
Train dispatchers to only use the new Branch Location moving forward
Wait… After about 1 month, check all OPEN tickets with out new Branch Location and address these 1 by 1 (gross, I know).
After reconciliation of all OPEN tickets, delete old Branch Locations as available. Hopefully not going over 1.5 months after creating the new Branch Location.
Thank you for the update on this process. What will be the command to run an update Import scenario to update the Branch Location? I have created an Import scenario. When I run it the import show that the Branch for the Service order was updated.
On the Service Order and appointment the branch location still exist as prior to the Update Import scenario. I dot not see an action on the import scenario to force the select on the branch location.
@rethavanalphen11, I was able to accomplish this using Mass Update for the Service Order Generic Inquiry, and double checking the Appointment Generic Inquiry as well for any open tickets with the wrong branch location.
You will only be able to change the Branch Location on Service Orders that have never had an appointment created, or if they have 1 appointment, that appointment can’t have been started. Once an appointment is started on a Service Order the Branch Location field is locked, not allowing it to change.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
