You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The Curb Event model has many ID fields that are all UUIDs, but we have found when working with partners that they very often do not use UUID identifiers internally.
Describe the solution you'd like
It would be nice to have fields on the Curb Event model where they could put those internal identifiers. These are existing fields where it would be nice to have a plain-text addition to hold vendor internal IDs:
event_id
event_session_id
data_source_device_id
Maybe we could create vendor_ prefixed versions of these that are string fields.
Is this a breaking change
No, not breaking
Impacted Spec
For which spec is this feature being requested?
Events
Describe alternatives you've considered
Alternatively, we could change the existing ID fields to be strings, but this would make them less likely to be globally unique across regions and vendors.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The Curb Event model has many ID fields that are all UUIDs, but we have found when working with partners that they very often do not use UUID identifiers internally.
Describe the solution you'd like
It would be nice to have fields on the Curb Event model where they could put those internal identifiers. These are existing fields where it would be nice to have a plain-text addition to hold vendor internal IDs:
event_id
event_session_id
data_source_device_id
Maybe we could create
vendor_
prefixed versions of these that are string fields.Is this a breaking change
Impacted Spec
For which spec is this feature being requested?
Events
Describe alternatives you've considered
Alternatively, we could change the existing ID fields to be strings, but this would make them less likely to be globally unique across regions and vendors.
Additional context
N/A
The text was updated successfully, but these errors were encountered: