Community & Venue Geofences – Breaking Change Notification
July 1, 2026
_____________________________________________________________________________________________
|
UPCOMING BREAKING CHANGE
In the June 2026 release (v2026.06), the Community & Venue Geofences product family will adopt the SPL Alternate Identifiers (ALTID) and introduce PreciselyID and Parent PreciselyID structure. This is a breaking change for six products (Airports, Auto Dealers, Colleges, Golf Courses, Hospitals, and Shopping Boundaries). Customers should read this notice in its entirety.
|
Abstract
This notice follows the March 2, 2026, communication regarding upcoming breaking schema changes to the Precisely Community & Venue Geofences products. The intent is for this announcement to provide more clarity on the technical details of these changes. Please read this message in its entirety if you license Precisely Community & Venue Geofences products.
Overview of Features and Functionality
What is a breaking change?
We define a breaking change as any addition, removal, or renaming of attributes; or any change that we believe would affect a client's ETL scripts. Because we know how impactful a breaking change can be to your production process, we limit them to once a year. We provide these notices so that you may appropriately plan to update your production systems as necessary.
When?
These changes will be effective this June 2026 Community & Venue Geofences product release (v2026.06).
Products with a Breaking Change
All six Community & Venue Geofences products are affected by this release.
· Airports
· Auto Dealers
· Colleges
· Golf Courses
· Hospitals
· Shopping Boundaries
What Is Changing
PreciselyID and Parent PreciselyID will be introduced as SPL Alternate Identifiers (ALTID) on every Community & Venue Geofences product. The ALTID table uses the following structure:
|
field_name
|
field_friendly_name
|
description
|
|
ALTID_ID
|
Alternate ID Identifier
|
Alternate identifier record ID.
|
|
OBJ_ID
|
Object ID
|
Unique and permanent object ID.
|
|
ALTID
|
Alternate ID
|
Alternate identifier value.
|
|
ALTID_TYP
|
Alternate ID Type
|
Type of alternate identifier (for example, PreciselyID or Parent PreciselyID).
|
Within the ALTID and ALTID_TYP fields, PreciselyID and Parent PreciselyID will be introduced. The PBKEY and PARENT values are recorded in the corresponding ALTID field within the table.
About PreciselyID and Parent PreciselyID
The PreciselyID is a unique and persistent identifier for an address location. Primary address records with associated secondary address records (units, apt etc.) are related to creating parent/child relationships. PreciselyIDs will be introduced as Alternate Identifiers (ALTID) to support flexible, one-to-many relationships with other data products across the Precisely data portfolio. For a given ObjectID a complete list of PreciselyIDs is provided to represent all addresses associated to that object. If there are parent/child relationships for a given object, this will be identified within the ALTID_TYP field.
Sample ALTID example from Palm Springs Airport:
|
ALTID_ID
|
OBJ_ID
|
ALTID
|
ALTID_TYP
|
|
422560900
|
22501822
|
P00002TU0AM1
|
PreciselyID
|
|
422560901
|
22501822
|
P00002TU0AM2
|
PreciselyID
|
|
422560902
|
22501822
|
P00002TU0AM3
|
PreciselyID
|
|
422560903
|
22501822
|
P00002TU0AM4
|
PreciselyID
|
|
422560904
|
22501822
|
P00002TU0AM6
|
PreciselyID
|
|
422560905
|
22501822
|
P00002TU35NF
|
PreciselyID
|
|
422560906
|
22501822
|
P00002TU35NG
|
PreciselyID
|
|
422560907
|
22501822
|
P00002TU9U5Q
|
PreciselyID
|
|
422560908
|
22501822
|
P00002TU9U5R
|
PreciselyID
|
|
422560909
|
22501822
|
P00002TU9U5S
|
Parent PreciselyID
|
|
422560910
|
22501822
|
P00002TU9U5S
|
PreciselyID
|
Why We Are Making This Change
· Improve interoperability across Precisely Enrich products.
· Deliver greater consistency, performance, and long-term scalability.
Action
Review the updated data schema and be sure to check our Help Center at https://help.precisely.com/home.
Contact Information
If you would like technical assistance, please contact the Precisely Global Support team at Contact Support - Precisely Support.
Product documentation is available in the Precisely Help Center at help.precisely.com.
For full reference detail - schema, worked examples, and per-product guidance - see the Community & Venue Geofences Product Start Guide, which will be available in the Help Center with the June release.
Any questions relating to this notification can be directed to:
Can Coskun
Associate Product Manager
can.coskun@precisely.com
2026 © Precisely. All rights reserved.