Skip to main content
Avoiding Duplicate Entries

SwiftComply's best practices to avoid duplicate records and avoid potential fees.

Updated over a week ago

Access: Service Providers

Overview: A review of best practices to avoid entering duplicate data into SwiftComply Backflow.

Topics:

Video: Best Search Practices

Avoiding Duplicate Entries:

Avoiding duplicate entries is essential to keeping clean and accurate data.

Duplicate data in SwiftComply is often caused by creating a new location or new assembly records while submitting test reports, without going through the proper procedures of searching for those records first.

When searching for an address or backflow device, less is more! It's best to use fewer characters to get more search results.

It's common that addresses aren't in the system exactly the way you expect them to be which can throw off your search results. For example First Street could be written like 1st Street, First St, etc.

See the example below of searching for the location address 1125 SE Division St.

You'll see that typing in the full address wasn't successful, but typing in just the number returned several options.

*Click the image above to enlarge the example

slightly smiling face emoji
slightly smiling face emoji

Did this answer your question?