Issue
Crash Magic has a new feature that allows for agency selection in the study panel. This can often eliminate the need for the Unique1 and/or Unique2 attributes. PdMagic is proceeding to update our client configurations to remove the use of Unique1/2 where appropriate.
Explanation
The Unique1/2 properties used to be a requirement for clients that had data from multiple agencies. This included any agencies that imported and/or entered data from neighboring agencies to be sure border crashes weren’t excluded from their studies. It is now only (sometimes) needed for agencies like counties or states, that have multiple identical street names in different cities that represent different streets. (e.g. Main St exists in each of two nearby cities, but is a different physical road in each) Even in that case we have other solutions that are more convenient.
A new option in the program provides for a checkbox in the study panel called “limit study to specific agencies”. Enabling it presents a list of all the agencies in the current database. So if your agency is Mesa, AZ and you also import data for Chandler, Scottsdale and Phoenix, you no longer need to use the “unrestricted” study or see street names like “Broadway (Mesa)” in your lists. In Eugene you won’t have have a city or county qualifier either. In all agencies in Colorado, this was occurring in the background but most users never had to see “Street name (county)”. If you did, you don’t any more.
In order to take advantage of this and eliminate the need for Unique1/2 in your configuration, PdMagic will rework your configuration to remove the City/County from the database. We will also merge all of your otherwise identical street names. (e.g. Broadway (Mesa) and Broadway (Scottsdale)) Then we will enable the use of “limit study to specific agencies” for your configuration.
For most agencies, this process is only a bit tricky and takes a day or so. For agencies with shared configurations (like AZ, CA, CO, OR, etc.) we have to make the change gradually while keeping others that also use that configuration still running without errors. That takes planning and time.
Solution
There is nothing that any agencies need to do. Our process has been to create a temporary configuration for clients to use as they are switched over and then update the main configuration when all affected client systems are upgraded. We do present a box on the login panel that says your account has been disabled while we make this move. That box should only be displayed for 10-15 minutes and we do our best to complete the work when no one is logged in.
Status:
- On 10/09/2026 We completed the Colorado DR3447 configuration migration and all agencies in Colorado are now using the new system. Several agencies have been using the new system for months and others just switched over on Friday.
- Our plan is to address AZ, CA, OR in that order unless we hear from someone in urgent need of the upgrade. We’ll continue to update this section of the article until the process is complete. All new configurations will start with this feature enabled.
Please contact PdMagic if you experience any unexpected behavior with streets such as high crash location lists, data entry or street name selection.
0 out Of 5 Stars
| 5 Stars | 0% | |
| 4 Stars | 0% | |
| 3 Stars | 0% | |
| 2 Stars | 0% | |
| 1 Stars | 0% |