Who this article is for: Authority Users
Overview
SwiftComply lets your organization track data beyond the standard fields on assemblies and locations using two field groups:
Custom Properties β fields specific to your organization, configured by SwiftComply during setup.
State Report Properties β fields required by your state's backflow reporting rules, configured for states SwiftComply has set up a report template for.
State Report Properties exist on both assemblies and locations, depending on what your state's report requires. This article walks through where to find them, how to edit them, and the field types supported.
Custom Properties on Assemblies
What They Are
Custom Properties are fields specific to your organization. SwiftComply configures them on your behalf during setup. They capture data beyond the standard backflow fields β things your program needs to track but that aren't part of SwiftComply's built-in schema.
Common examples (these vary by org):
Meter Account #
Lead Free?
Protection Type
Hazard
Supported Field Types
Field Type | How It Behaves |
Text input | A single-line text field |
Textarea | A multi-line text field for longer notes |
Select | A dropdown with pre-configured options |
Checkbox | A single on/off checkbox |
Date | A date picker |
Past date | A date picker that only accepts dates on or before today |
Where to Find Them
On an assembly's detail page:
Click Assemblies in the left navigation and open any assembly.
The DETAILS tab is selected by default.
Scroll to the Custom Properties accordion (expanded by default if your org has Custom Properties configured).
If your organization doesn't use Custom Properties, the accordion won't appear.
Updating Custom Properties Values
Open the assembly from the Assemblies table.
On the DETAILS tab, click Edit.
In the Custom Properties section, update the fields you need to change.
Click Save.
π‘ Custom Properties also appear as columns available to add to the Assemblies table, grouped under Equipment Details in the Table Columns gear menu. They're also available as search and filter criteria β use the search field's field selector or the Advanced Filter Builder to find assemblies by any Custom Property value.
State Report Properties on Assemblies
What They Are
State Report Properties are fields your state requires on backflow assemblies for regulatory reporting. They appear only when your organization's state (set on your organization's profile) has a configured state report. Currently, state-specific fields are configured for these states:
California (CA)
Colorado (CO)
Florida (FL)
Massachusetts (MA)
Michigan (MI)
Washington (WA)
Values entered in these fields are used to populate the end-of-year state report, viewed from State Reports in the left navigation. For the end-to-end flow, see How State Reporting Works in SwiftComply and Running and Generating State Reports.
Updating State Report Properties Values on an Assembly
Open the assembly from the Assemblies table.
On the DETAILS tab, click Edit.
In the State Report Properties section, update the fields.
Click Save.
π‘ Track State Report Properties throughout the year rather than trying to fill them in right before the report is due. Doing it as you go avoids a scramble at year end.
State Report Properties on Locations
Some states require data at the location (premise) level in addition to (or instead of) assembly-level data. The most common example is Washington, which requires premise-level information that isn't tied to a specific assembly.
When your state's template includes location-level fields, those fields show up on the location's detail panel as their own State Report Properties section. They're also searchable from the Locations search panel β you'll see fields prefixed with `srp:` (for example, `srp:connections`, `srp:hazard_type`, `srp:npdes_permit`).
Updating State Report Properties Values on a Location
The flow mirrors the assembly side:
Open the location from the Locations list.
On the DETAILS tab, click Edit.
Update the State Report Properties fields.
Click Save.
Whether your state has location-level fields, assembly-level fields, or both is determined by the state report template SwiftComply has configured for your organization. If you're unsure, check both record types or ask your CSM.
FAQ
Q: Can I add new Custom Properties myself?
A: Custom Properties are configured by SwiftComply at the organization level, so they can't be set up on your side. If you need a new field added, renamed, or removed, reach out to your CSM and we'll take care of it.
Q: My state isn't in the supported list. Can I still use State Report Properties?
A: State Report Properties are only available for states SwiftComply has configured. If your state needs to be added, let your CSM know and we'll scope the work.
Q: Do I need to fill in State Report Properties on both the location and the assembly?
A: It depends on your state's template. Some states only require assembly-level fields; others require location-level fields; some require both. Whichever fields appear on your records are the ones the report will use. If you're unsure, ask your CSM which fields apply to your state.
Q: Do State Report Properties values affect an assembly's compliance status?
A: No. State Report Properties are used for state regulatory reporting only β they don't drive an assembly's Overall Compliance status. Compliance is driven by Last Test Result and Next Test Due on the assembly's compliance record. See Understanding Assembly Compliance Status for details.
Q: How are Custom Properties values used beyond the DETAILS tab?
A: Each Custom Property can be:
Displayed on the DETAILS tab under Custom Properties
Added as a column on the Assemblies table (from the Equipment Details group in the Table Columns menu)
Searched for from the search field's field selector
Used in Advanced Filter Builder rules