Comments
CoPilot suggested I add this sentence:“If you’ve ever tried to maintain a true Master Production Schedule using Supply Forecasts and a Frozen time fence, this Idea fixes a behavior that breaks it today.”I also wanted to add that I was told that that one of the main reasons a Supply Forecast existed in AX (I used it in 3.0) was for purchased items to model a Supplier with a limited capacity, to see, in planned orders, their capable deliveries. MPS would critique these with Action Messages and add new planned orders where they did not suffice. These new planned orders would be candidates for alternate sourcing. By the way this was a legacy "trick" to cope with multiple sourcing before Microsoft added the new source by percentage capability. Forcing these forecasts (i.e. the planned orders they would spawn) to beyond the Frozen time fence ALSO makes little sense, whether modelling a constrained supplier or modelling multiple sources.
When you have a Journey with a step to create an Opportunity, if this opportunity creation fails, CIJ only shows that the opportunity creation step “Exit” but it doesn’t show any errors. The only way to check the error is to open the Power Automate flow related to this Journey and review the run that has failed to see the error. The suggestion is to have CIJ show this error so that it’s easier for users to handle it, similar to the errors that appear when emails bounce, you can easily see the failures.
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
Each time a journey is created or edited, a new power automate flow is created. We now have well over 20k flows that were created by journeys. My suggestion is to delete flows when a journey is deleted or if a new edit is made, delete the prior version. Having this many flows crowds our solution and takes a toll on our capacity.
As per the doc Known issues in Customer Insights - Journeys with mitigations - Dynamics 365 Customer Insights | Microsoft Learn on Microsoft Learn, a single wait tile in a journey cannot extend beyond 90 days. However, the customer would like the option to increase this wait duration, as certain contacts—such as university students enrolled in a 3-year degree program—need to remain in the wait tile for extended periods to support longer-term journeys.
Currently we can only set the number of days between two iterations of a recurring customer journey. We would like to have the possibility of setting also the number of months between two iterations, so that the customer journey could iterate for example the 1st of each month, since the number of days in a month is not always the same and we cannot use a fixed number of days in this case