June 2, 2026

These release notes describe all user-facing changes that will be included in the next Axon Records and Standards releases, along with advance notice of major upcoming features, updates, and applications.

There are three releases scheduled for June:

• June 2, 2026
• June 16, 2026
• June 30, 2026

These notes include all items in the June 2 release. Additional notes will be sent later in the month detailing all information for the remaining June releases.

Releases begin rolling out at 11 AM Pacific time and may continue through the following day. We do not expect any downtime during these updates. Please note that availability is subject to change. Depending on the complexity and amount of items included in a release, some items in these notes may not be available until two days after the release.

Additional help documentation for Axon Records and Standards is located at axon.com/help. Do you have feedback about Axon's release notes? Submit it here.

Download this month's release notes

Records preview release

This section includes information about upcoming features and updates that are available for testing in training environments. These are beta features, and all functionality may not be fully present or completely reliable.

There are no preview release items for Records in the June 2 release.

Records general release

This section includes information about upcoming features and updates that are available in all production environments.

Task Inboxes

The following feature will be available for all organizations to use in their production environments on June 2, 2026. Contact your Axon representative or Axon Support to activate it for your organization.

• You can now work with Axon Support or your Axon representative to disable routing notes for reports that move through specific workflows.

Report Writer

The following update will be applied to the production environments of all organizations on June 2, 2026.

• The incident report deletion behavior has been updated so that incident reports can now be deleted once all property items have been removed from them.

Search

The following update will be applied to the production environments of all organizations on June 2, 2026.

• Search performance has been improved so that search results load more quickly when you open a profile or report from search and then return to the search page.

Form Builder

The following update will be applied to the production environments of all organizations on June 2, 2026.

• You can now use a new Restore previous version as a draft action in Form Builder. This feature lets you undo the most recently published changes for a form by restoring the form to the previously published version.This feature introduces a safeguard to allow you to roll back form changes in case incorrect or undesired changes were published.
  • To initiate this action, open a form and select More Actions […] > Restore previous version as a draft. When triggered, the revert action discards the current unpublished draft and creates a new draft using the most recently published version—the one that was live before the latest publish. You can then review, adjust, and re-publish this restored version as needed. This action is logged in the Form Builder activity log, recording who performed the revert and when.
  • Key details:
    • You can only revert to the version most recently published (before the current published version).
    • The feature is available for forms with at least one prior published version.
    • A warning message appears before confirming the revert, explaining that any changes in the current draft will be lost.
    • If you revert a form and a new draft is generated, you must discard this new draft to return to the latest published version instead.

Records resolved issues

This section includes information about upcoming bug fixes and resolved issues that will be released to all production environments.

Report Writer

The following issue will be resolved on June 2, 2026.

• Previously, offense information was not displayed correctly when a Person > View arrest was selected on an incident profile page. This issue has been resolved, and now the offense selected in the incident report is displayed as expected.

Search

The following issue will be resolved on June 2, 2026.

• Previously, Location search would occasionally fail to return results based on how the search query was entered in the search box. This issue has been resolved, and Location search functions as expected.

NIBRS

This section includes information about upcoming updates and bug fixes for NIBRS validation rules, errors, and submissions.

Arizona organizations

The following update will be applied to the production environments of all Arizona organizations on June 2, 2026.

• Several issues have been resolved where Arizona NIBRS submissions were rejected by the state due to formatting problems in the submission file:
  • Error 0307 — The Property segment for "1 - None" property values was reporting too long, and Drug Type was duplicated. Property length and Drug Type values are now reported correctly, preventing the rejection.
  • Error 0111 — The Arrest segment was not reporting demographic information for a second arrestee when the incident's primary offense was a Group A offense and a Role was linked to a Group B (or non-reportable) offense. All arrestee demographic information is now correctly included in the submission.
  • Error 0082 — The Race field was not populating on submission, which shifted subsequent fields to the left and caused state validation errors. The Race field is now correctly populated, preserving the position of all subsequent fields.
  • If your organization has received any of these rejections, please contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents requeued for submission.

California organizations

The following update will be applied to the production environments of all California organizations on June 2, 2026.

• An issue has been resolved where the Property Value field was incorrectly required on California NIBRS incidents when the Property Loss Type was set to 1 (None). Property Value is not reported when no property is involved and should not be required in that case.
  • Users can now save an incident with Property Loss Type 1 (None) without entering a Property Value.
  • No action is required. The validation will be updated automatically.

Louisiana organizations

The following updates will be applied to the production environments of all Louisiana organizations on June 2, 2026.

• Louisiana NIBRS submission files now include Group B / 90-series offense incidents (for example, 90A, 90Z) per guidance from the Louisiana Incident-Based Reporting System (LIBRS) program. Group B offenses are now treated the same as Group A offenses in the submission file, with all required data elements and segments included regardless of whether an arrest is associated with the incident. The state will retain Group B incidents at the state level until an arrest is recorded before forwarding them to the FBI.
  • No action is required. Group B incidents going forward will be included automatically. If your organization would like prior Group B incidents resubmitted, please contact Axon Support or your NIBRS Customer Support Specialist.
• A validation rule has been added for Louisiana NIBRS submissions to prevent state rejections on incidents with a 13B (Simple Assault) offense. The Louisiana Incident-Based Reporting System (LIBRS) requires a weapon or force to be reported for 13B offenses, with an acceptable Type Weapon/Force Involved value of 40 (Personal Weapons), 90 (Other), or 95 (Unknown).
  • Previously, users could submit a 13B offense with "Was Weapon/Force Involved" set to No, which resulted in the state rejecting the submission. Users will now see a validation error if a 13B offense does not include a weapon/force value of 40, 90, or 95, preventing the rejection before submission.
  • No action is required. The validation rule will be applied automatically. If your organization has received state rejections related to missing weapon/force on 13B offenses, please contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents updated and requeued for submission.

Maryland organizations

The following updates will be applied to the production environments of all Maryland organizations on June 2, 2026.

• An issue has been resolved where only one Location Type was included in the NIBRS submission file when an incident contained offenses with different Location Types. This caused the submission to be rejected because the reported Location Type did not match all offenses on the incident. All applicable Location Types are now correctly included in the submission file.
  • If your organization received rejections for this error, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents requeued for submission.
• An issue has been resolved where NIBRS submissions were rejected with error 084 (recovered property value cannot exceed stolen property value). The stolen property total in the submission file was calculated lower than the value displayed on the report, causing the recovered amount to appear greater than the stolen amount. This could occur when a property item's role did not align with its property status type. The stolen property total is now calculated correctly in the submission file, matching the report.

Minnesota organizations

The following updates will be applied to the production environments of all Minnesota organizations on June 2, 2026.

• To better match how NIBRS submissions are organized and to improve the report-writing workflow, the Location Category and Location Category Description fields have been moved from the Overview card to the Offense card on Minnesota incidents. Both fields remain tied to the offense's UCR code and continue to follow the existing visibility and required-field rules.
  • Users can now enter location information at the same step where they enter offense details, without needing to return to the Overview card after selecting a UCR code.
  • No action is required. The updated layout will appear automatically on new reports.
• An issue was resolved where Minnesota NIBRS submissions returned Bureau of Criminal Apprehension (BCA) warnings that a Vehicle Make Code, Vehicle Model Code, or the Make/Model combination was not valid per the NCIC manual, causing the field to not be stored in the state's investigative database (LEIS).
  • When entering vehicle information, the Vehicle Model field is now filtered based on the Vehicle Make selected and will only display valid NCIC Make/Model combinations. This ensures every vehicle submitted to the BCA contains a valid Make, valid Model, and valid Make/Model combination.
  • If your organization received warnings related to invalid Vehicle Make or Model values, contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents updated and requeued for submission.

Virginia organizations

The following update will be applied to the production environments of all Virginia organizations on June 2, 2026.

• An issue has been resolved where Virginia NIBRS flat file submissions were rejected by the state because unexpected trailing characters were appended to specific record lines. In affected records, internal identifier values were being written into the file in place of (or alongside) the correct coded value at the end of the offense record, causing the state to flag the submission as invalid.
  • The flat file is now generated cleanly, with each record line containing only the expected coded values and no extraneous identifiers.
  • If your organization has received state rejections for invalid flat file content, please contact Axon Support or your NIBRS Customer Support Specialist to have the affected submissions regenerated and requeued.
• Several issues have been resolved where Virginia NIBRS submissions were rejected by the state due to formatting problems in the submission file:
  • Error 0307 — The Property segment for "1 - None" property values was reporting too long, and Drug Type was duplicated. Property length and Drug Type values are now reported correctly, preventing the rejection.
  • Error 0111 — The Arrest segment was not reporting demographic information for a second arrestee when the incident's primary offense was a Group A offense and a Role was linked to a Group B (or non-reportable) offense. All arrestee demographic information is now correctly included in the submission.
  • Error 0082 — The Race field was not populating on submission, which shifted subsequent fields to the left and caused state validation errors. The Race field is now correctly populated, preserving the position of all subsequent fields.
  • If your organization has received any of these rejections, please contact Axon Support or your NIBRS Customer Support Specialist to have the affected incidents requeued for submission.

Standards preview release

This section includes information about upcoming features and updates that are available for testing in training environments. These are beta features, and all functionality may not be fully present or completely reliable.

There are no preview release items for Standards in the June 2 release.

Standards general release

This section includes information about upcoming features and updates that are available in all production environments.

Task Inboxes

The following update will be applied to the production environments of all organizations on June 2, 2026.

• Now, when a report is marked as Urgent, an Urgent label is added to the report when it is listed in task inboxes. These Urgent reports appear at the top of the task list in inboxes.

The following feature will be available for all organizations to use in their production environments on June 2, 2026. Contact your Axon representative or Axon Support to activate it for your organization.

• You can now work with Axon Support or your Axon representative to disable routing notes for reports that move through specific workflows.

Search

The following update will be applied to the production environments of all organizations on June 2, 2026.

• Search performance has been improved so that search results load more quickly when you open a profile or report from search and then return to the search page.

Form Builder

The following update will be applied to the production environments of all organizations on June 2, 2026.

• You can now use a new Restore previous version as a draft action in Form Builder. This feature lets you undo the most recently published changes for a form by restoring the form to the previously published version.This feature introduces a safeguard to allow you to roll back form changes in case incorrect or undesired changes were published.
  • To initiate this action, open a form and select More Actions […] > Restore previous version as a draft. When triggered, the revert action discards the current unpublished draft and creates a new draft using the most recently published version—the one that was live before the latest publish. You can then review, adjust, and re-publish this restored version as needed. This action is logged in the Form Builder activity log, recording who performed the revert and when.
  • Key details:
    • You can only revert to the version most recently published (before the current published version).
    • The feature is available for forms with at least one prior published version.
    • A warning message appears before confirming the revert, explaining that any changes in the current draft will be lost.
    • If you revert a form and a new draft is generated, you must discard this new draft to return to the latest published version instead.

Standards resolved issues

This section includes information about upcoming bug fixes and resolved issues that will be released to all production environments.

There are no resolved issues for the Axon Standards in the June 2 release.

Axon Notes Module preview release

This section includes information about upcoming features and updates that are available for testing in training environments. These are beta features, and all functionality may not be fully present or completely reliable.

There are no preview release items for the Axon Notes Module in the June 2 release.

Axon Notes Module general release

This section includes information about upcoming features and updates that are available in all production environments.

There are no general release items for the Axon Notes Module in the June 2 release.

Axon DataStore

This section includes information about upcoming changes to the Axon Records and Standards DataStore.

Updates

The following update will be applied to the production environments of all organizations on June 2, 2026.

• Now, in the DataStore Settings tool in the Administrator Console, DataStore administrators can give the Default Access Profile or Custom Access Profiles access to physical tables (dboRecords, dboStandards). This update only applies to organizations using DataStore v2.
  • Purpose: Designed for data replication accounts that require direct read access for replication tools.
  • Scope: Access is granted at the schema level (all tables within the schema).
  • Limitation: Fine-grained access (per-table) is not supported.