When creating custom triggers in Dynamics 365 Customer Insights - Journeys, all input parameters are treated equally. There's currently no way to specify whether a parameter should be mandatory or optional. This can lead to confusion, unintended behavior, or the need for additional workarounds.
Proposed Enhancement:
Introduce support for marking input parameters as either:
- Required: The trigger cannot be executed unless this value is provided.
- Optional: The trigger can still run even if this value is missing. Default values could also be supported.
What This Improves:
- Improved data validation and error handling at runtime
- Greater flexibility when integrating with external systems that might not provide all data fields
Comments
In Dynamics 365 Customer Insights – Journeys, when creating a Custom Trigger, attributes can only be defined by selecting a data type (Text, Number, Lookup, etc.).Currently, there is no capability to mark attributes as Mandatory or Optional. This limitation makes it difficult to enforce data validation and consistency when the trigger is invoked from Power Automate, plugins, or external integrations.Additionally, Option Set (Choice) data type is not supported for custom trigger attributes. This restricts the ability to pass controlled or predefined values, often forcing workarounds such as using free-text fields, which can lead to invalid or inconsistent data.Expected / Desired FunctionalityAbility to mark custom trigger attributes as Mandatory or OptionalBuilt-in validation to prevent trigger execution when mandatory attributes are missingSupport for Option Set (Choice) data type in custom trigger attributesOptionally, allow default values for optional attributes
Category: Event Triggers