# Notice of Change: Alert External ID and Entity Validation
Change Notice Date: November 6th, 2026
Change Target Date: November 20th, 2026
In the current model, when an external alert is raised, the External ID field accepts a free-text string of any format. No validation is applied to the value supplied, so clients may be using a variety of identifiers such as reference numbers, system-generated codes or other text values. This External ID was not propagated anywhere before this change. There are also further validation checks applied to the Entity.
What This Change Means for You as a Fenergo SaaS User
Following this change, the External ID will work as follows:
-
GUID format required: The External ID on an external alert must be a valid GUID (e.g. 3f2504e0-4f89-11d3-9a0c-0305e82c3301). Free-text strings will no longer be accepted.
-
Validation on alert creation: Validation is applied when an external alert is raised. If the External ID is not a valid GUID, the request will be rejected and the alert will not be created. However please note that the External ID is not mandatory, but if provided must be a valid GUID.
-
Advanced Reporting: The External ID is now available in Advanced Reporting. Going forward, values in this field will be in GUID format.
-
The entity validation change means that each message sent to the Event Ingress Create Alert business process goes through additional validations.
- The first validation is on the Event Ingress API and is synchronous. It checks the parity between the EntityId field in the top most scope and MainEntityId inside the payload property. These properties must match, and mainEntityId must be present in the payload as a valid GUID. In case of a mismatch (or a missing one) the appropriate response from Event Ingress will be returned.
- The second validation is inside the Create Alert Business Process. Main Entity will be validated against the Entity Data store, and in case the Entity is not found the request will be deemed failed, with the reason in the failure message. As this part is asynchronous, you will not see it in the Event Ingress response
Potential Impact to Clients
This may be a change for clients who currently supply a non-GUID string as the External ID. Those clients must update their integrations to send a valid GUID before this change takes effect, otherwise external alerts will fail validation and will not be raised. Key Points:
- The External ID on external alerts must now be a valid GUID.
- Validation is enforced when an external alert is raised; non-GUID values will be rejected.
- Clients using a free-text External ID must update their integrations to use a GUID.
- The External ID is now available in Advanced Reporting.
- The entity validation change means that each message sent to the Event Ingress Create Alert business process goes through additional validations.