Comments
I think this should be part of the base functionality, without the planning aspect. A lot of times when our customers ask for a sales quote they want to know both cost and lead time. Based on one of those, they may decide to go somewhere else. In order to accomplish this now (version 27.4) we have to convert the quote to an order, run CTP Order Promising, capture the date information, delete the sales order, go to sales order archives and restore the quote, then update the dates to provide to the customer. Crazy. If we could run a "non-planning" version of ATP/CTP in an order promising window right on the quote, we can give the customer what their looking for in a much more efficient way.
I think this also needs to be included anywhere Edit in Excel is present on transactions, such as Sales Orders, Purchase Orders, Sales Invoices, etc. Users are forced to enter this in manually and if they have transactions with lots of lines this creates a lot of work. Uploading via Edit in Excel would be so much simpler.
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