Comments
Yes, I have some multiple tickets which in the same situation. The guidance was reach to FTE but seems like the solution has to create new environment then clone through that new empty environment which is not an ideal option for most of the customers. Turn to an official feature is quite a good idea at the moment.
Fully support this idea. We come across this requirement very often in manufacturing and project-based businesses where customers make payments at different stages of an order. Since Business Central currently supports only a single prepayment percentage, many companies have to rely on customizations, Excel tracking, or manual adjustments.Having the ability to create and track multiple prepayments against the same Sales Order would make the process much simpler and more accurate. It would reduce manual work, improve visibility for users, and help organizations use standard Business Central functionality instead of building custom solutions. This would be a valuable enhancement for many businesses. 👍
Now we have year 2026 and it is still not solved. We have the same problem. Microsoft ignoring the needs of the customers. Microsoft does not provide us the possibility to maintain the database. Database is growing with data that is not needed any more. This costs the customers money (since we need more capacity). It makes D365 F&O slow (bigger database = slower)It makes maintenance slower (e.g. database copy)
We hit this same issue constantly - hundreds of Shopify exchanges/returns each requiring the same manual unlink → resolve conflict → recreate invoice steps. It's a huge time sink and error risk at our volume. We're actually considering a custom workaround just to avoid this, but would much rather see an automated/bulk conflict-resolution option added to the standard connector. Please prioritize this.