Comments
Notes and the notes FactBox are a small step in the right direction, but sometimes comments are extensive. The notes FactBox does not show all the comments, and you can't even see if the comment is complete or not because it's limited to what appears to be just 5 lines.In the 2.6 days, the comment popped out into a separate window, and as you went from document to document, card to card, the comment box that was popped out went along for the ride. Very convenient.We had to devise a Comment FactBox that we put on all our pages which effectively took care of this, however, it's at the top of most documents, and the first ListPart on a document page "gets the real estate" in the web client. This was not an issue in the RTC, so once again, this web client is making life worse for real workers. I'm curious to see what these planned improvements are that we should "stay tuned" about. I'd love to be reached out to for feedback prior to launching anything so I could show the team how real business users are trying to get the most out of this interface. We've been at this with Navision since 2002, so I think we'd have something special to offer here.
Hello, On French localization also, this feature disappeared : Apply general ledger entries The article related to is still in learn but our users can no longer use the feature because the button is gone. https://learn.microsoft.com/en-us/dynamics365/business-central/localfunctionality/france/how-to-apply-general-ledger-entries Our users are blocked. How can this problem be resolved ? Is it possible to restore this essential feature ? Thanks
This functional limitation in Dynamics 365 Finance regarding Direct Debit Mandates (SEPA) is causing significant operational, financial, and compliance issues for companies working with multiple company bank accounts under the same creditor identifier (Direct Debit ID). Today, D365 Finance forces the mandate to be linked to a single company bank account, even when the creditor identifier (Direct Debit ID) is the same across all company bank accounts. As a result, customers must sign multiple mandates, and users must manually select the correct mandate depending on which company bank account is used for settlement.This behavior is not aligned with SEPA standards, where one mandate per customer per creditor should be sufficient—regardless of how many bank accounts the creditor uses.This limitation impacts organizations that operate with multiple bank accounts due to treasury optimization, discount lines, credit facilities, or multi-bank strategies. The consequences include:Additional administrative effort. Companies must manage and store 2–10× more mandates per customer depending on the number of bank accounts used.Manual errors in mandate selection. Risks increases in high volume payment environments. This process is critical for many business and companies.Slower onboarding, Take longer to create a customer. Time to create a mandate increases 2–10× per customer depending on the number of bank accounts used.Inefficiency in collections. Finance teams spend significant time validating which mandate applies to each transaction.
Absolutely critical to be able to impose rate limiting, not only for static journeys but also for recurring journeys. In the case a user were to specify a journey to recur faster than the journey can complete, then terminate the previous run before the journey recurs. Perhaps some sign-posting to users to ensure they consider the interaction between the timing of the rate limiting and the timing of the recurrence.
