Who this article is for: Authority Users
Overview
This article covers how to manage assembly locations — including assigning, changing, and removing locations, as well as replacing one assembly with another. Where relevant, it notes what data is preserved or lost during each action.
Changing an Assembly's Location (Moving)
If an assembly has been physically moved to a new location, you can update its location in SwiftComply without losing any historical data.
Navigate to the assembly's detail page.
Click the Location tab.
Click Actions, then the Change Location button.
The location selection pop-up opens with the current location highlighted.
Search or browse the list to find the new location.
Select the new location and click Change Location.
A confirmation pop-up appears.
To confirm the change, click Change Location.
💡 All test history, compliance data, and communications are preserved when you move an assembly. Only the location association changes.
Assigning a Location for the First Time
If an assembly does not yet have a location assigned, you can assign one from the assembly's detail page.
Navigate to the assembly's detail page.
Click the Location tab.
Click the Assign Location button.
The location selection pop-up opens with a searchable table of available locations.
Select the desired location.
Click Assign Location.
Replacing an Assembly
When a physical backflow assembly is replaced with a new one, SwiftComply lets you link the new assembly to the one it replaced. There are two ways to do this.
Replacement Method | Best Used When |
Replace from existing assembly | You are starting from the old assembly's page |
Mark during creation | You are creating the new assembly first |
Option 1: Replace from an Existing Assembly
Navigate to the assembly that is being replaced.
Click the Details tab.
Click Actions, then click Replace.
A pop-up opens where you can search and select the replacement assembly.
Click Save.
Option 2: Mark as Replacement During Creation
When creating a new assembly, check the Replacement checkbox.
A pop-up with a search field appears. Search and select the assembly that this new one is replacing.
Optionally, check Set replaced assembly as inactive to automatically deactivate the old assembly.
Click Save.
💡 Marking a replaced assembly as inactive during creation saves you from having to manually deactivate it afterward. This is the recommended approach.
Removing an Assembly from a Location
You can remove an assembly from its current location without assigning it to a new one.
Navigate to the assembly's detail page.
Click the Location tab.
Click Actions, then Remove from Location.
A confirmation pop-up will open. To confirm removal, click Remove from Location.
⚠️ When you remove an assembly from a location, the Installed On date and Assembly Location text are permanently lost and cannot be recovered. Make sure you want to proceed before confirming.
What Data Is Preserved?
Action | Test History | Compliance Data | Communications | Installed On Date | Assembly Location Text |
Change Location (Move) | Preserved | Preserved | Preserved | Preserved | Preserved |
Assign Location | Preserved | Preserved | Preserved | Preserved | Preserved |
Replace Assembly | Preserved on both old and new | Preserved on both | Preserved on both | N/A | N/A |
Remove from Location | Preserved | Preserved | Preserved | **Lost** | **Lost** |
FAQ
Q: Can I move an assembly to a location that already has other assemblies?
A: Yes. A location can have multiple assemblies assigned to it. Moving an assembly to an occupied location does not affect the other assemblies there.
Q: What happens to the old assembly's compliance status after it is replaced?
A: The old assembly retains its compliance history. If you checked Set replaced assembly as inactive during replacement, it will be marked inactive and will no longer appear in active compliance tracking.
Q: Can I undo a removal from a location?
A: You can reassign the assembly to a location using the Assign Location button, but the original Installed On date and Assembly Location text are not recoverable. You would need to re-enter those values manually if applicable.
Q: Is there a way to bulk-move multiple assemblies at once?
A: Currently, assemblies must be moved individually. Each move requires confirmation to prevent accidental changes.