Comments
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
In the properties area of the tile "Send an email", where one has to choose the email to send, we should also have the possibility to overrule the "To:" defined in the email itself. If we want to send the email to both emailaddress1 and emailaddres3 of a contact, we now need to create the email a 2nd time, just to be able to send to another "To:". This is not user friendly.In our case where each email exists in 4 languages already, then times 2, that is a lot of emails. (We use emailaddress3 to store the contact's assistant email address)
Make it possible to update an attribute on a Contact or Lead directly within a journey, similar to how attributes can be updated within Sequences in Sales Hub.Using the Update Dataverse record action with in a journey , you should be able to select the attribute you want to update and set its value. The value can be defined as either:Static, orDynamic, using data from the journey trigger.For example:You could populate a “Last marketing email sent on” field by setting the date at the point the email action is triggered within the journey. to add the date when the action is triggered,