on
RE:
This is a major issue we're experiencing as well. We need to be able to edit live segments based on growing audience over time. There is only so much pre-planning that can be done when building the segment when we are creating long term nurture content. On Microsoft's known issues they say "Today, users can't edit a segment that is being used in a live journey in Customer Insights - Journeys. To be able to edit the segment, stop the journey, and then make the edits to the segments." This makes it seem like we can pause the journey and restart it after finishing segment edits. However, this is not the case. When we go to stop the journey we get a warning "Once this journey is stopped, it cannot be restarted. A stopped journey has to be recreated before going live." This is a huge amount of extra work for functionality we had in Outbound already.
RE:
This is a major issue we're experiencing as well. We need to be edit live segments. On Microsoft's known issues they say "Today, users can't edit a segment that is being used in a live journey in Customer Insights - Journeys. To be able to edit the segment, stop the journey, and then make the edits to the segments." This makes it seem like we can pause the journey and restart it after finishing segment edits. However, this is not the case. When we go to stop the journey we get a warning "Once this journey is stopped, it cannot be restarted. A stopped journey has to be recreated before going live." This is a huge amount of extra work for functionality we had in Outbound already.
RE:
For further clarifying please refer to the below comment:In standard D365FO, when creating a purchase requisition, D365FO selects prices based on trade agreements with the lowest unit price without considering available discounts. If there are two purchase price journal trade agreements with prices of 20 USD (vendor 1) and 15 USD (vendor: Vendor 2) respectively. Additionally, there are two line discount trade agreements offering discounts of 50% (vendor 1) and 10% (vendor 2). The system currently selects vendor Vendor 2 with a unit price of 15 USD for the purchase requisition. However, considering potential discounts, vendor Vendor 1 offers a better net amount as its unit price after applying a discount would be 10 USD (20 – (50% * 20)). Desired Behaviour: The system should retrieve and apply prices based on both unit prices and any available discounts to determine and select the lowest net amount.
RE:
Yes please! This would be a great improvement.
RE:
We did automate this if you want to look at it.https://azuremarketplace.microsoft.com/en-us/marketplace/apps/trunorthdynamics2.trunorth-unlocked-er?tab=overview
RE:
Absolutely great Idea!Its a real pain to work with the API capabilities of Business central if you have to integrate complex solutions like webshops, warehousing software and others.
RE:
This is Requriement from most of customers
RE:
Yup.. My client to have to face this issue, for now they are managing this Manually. It would be better if Microsoft Focus on Less Manual Tasks and more towards Automated Tasks.Pay TDS is not optimized if we have to manually change other setups to use intended Functionality.
RE:
Business Central Should have this feature, as for ever Posted Purchase Invoice Reversal, user have to post TDS Adjustment Journal. which creates confusion on TDS Adjustments and TDS ReversalsHope, Microsoft understands the pain area of not having this Functionality
RE:
I cannot believe this feature is not in place yet.