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
Handle duplicate device entries - Right now we can end up with duplicate device entries in the database. To fix this, add a unique ID (GUID) column to the device table. Before inserting a new device, check if a record with the same GUID already exists — if it does, update it instead of creating a new entry. This way we avoid duplicates and keep the data clean.
Device table schema update -Update the device table to include the new columns we need for better device tracking and lifecycle management:
- device_added_date — when the device was added
- soft_delete — flag to mark device as deleted without removing the record
- provisioning_status — current provisioning state of the device
- device_info — additional device metadata
Add a variable that clearly defines the deployment mode — enterprise, cloud, or hybrid. This variable should strictly control what kind of devices can be added based on the mode. Right now, both enterprise and cloud devices can be added when CIRA is enabled — this should fix that. For example:
- enterprise mode → only enterprise devices allowed
- cloud mode → only CIRA/cloud devices allowed
- hybrid mode → both allowed
Handle duplicate device entries - Right now we can end up with duplicate device entries in the database. To fix this, add a unique ID (GUID) column to the device table. Before inserting a new device, check if a record with the same GUID already exists — if it does, update it instead of creating a new entry. This way we avoid duplicates and keep the data clean.
Device table schema update -Update the device table to include the new columns we need for better device tracking and lifecycle management:
- device_added_date — when the device was added
- soft_delete — flag to mark device as deleted without removing the record
- provisioning_status — current provisioning state of the device
- device_info — additional device metadata
Add a variable that clearly defines the deployment mode — enterprise, cloud, or hybrid. This variable should strictly control what kind of devices can be added based on the mode. Right now, both enterprise and cloud devices can be added when CIRA is enabled — this should fix that. For example:
- enterprise mode → only enterprise devices allowed
- cloud mode → only CIRA/cloud devices allowed
- hybrid mode → both allowed