What’s happening?
Users are unable to create events with an end date beyond June 20025 via UI or API. Attempts to create such events result in an error, specifically an InvalidPluginExecutionException indicating that the localization label "EndDateIsAfterObmDeprecationDateFormat" was not found. This can also occur when creating events from templates.
Reason:
This occurs because the Dynamics 365 Customer Insights - Journeys Outbound Marketing module will be deprecated on June 2025. The system has a built-in validation (ObmDeprecationValidationStrategy) that prevents creating Outbound Events with an end date beyond this deprecation date. The specific error encountered ("InvalidPluginExecutionException") is due to a missing localization label ("EndDateIsAfterObmDeprecationDateFormat") in the web resource "msevtmgt_/Localizations/plugins1033".
Resolution:
This behavior is a product limitation by design. Outbound Events cannot have an end date later than June 2025 due to the planned deprecation of the Outbound Marketing module.
To resolve or avoid this issue:
- When creating or updating an Outbound Event, ensure the event's end date is set to a date before June 2025.
- To determine whether an event is Outbound or Real-time, check the event's "msevtmgt_sourcesystem" field:
- If the "msevtmgt_sourcesystem" field indicates an Outbound event, the end date must be before June 2025.
- If the "msevtmgt_sourcesystem" field indicates a Real-time event, you can select an end date after June 2025.
For more information on the Outbound Marketing transition to Real-time Marketing, see: Transition Overview | Microsoft Learn.