Experienced the same. The ability to update journeys and make new versions is very nice. However, that we cannot force versions that are in the compliting stage, prevents us from using this functionality, due to risk of customers being stuck in an outdated journey.
This must surely have implications with GDPR also. If D365 is not processing the data in the same manner across all channels there is then a discrepancy especially in the instance a customer requests what data is held on them or the right to erasure.
Agree, this is something BC should provide that there is not a difference in the process for the users. No matter for what the receipt is or where the purchase order is originated from.
Without any explanation, this change in functionality looks to be totally unwarranted and is creating additional unnecessary workload for our customers.
Can a rationale for the change be provided please plus an indication of the likelihood of it being reversed?
