Comments
Hi Business Central Team,
you ask: "What if you accidentally create an account, post an entry, discover mistake and post a reverse entry - the new account was a mistake, not needed, will never be used again...should you still be able to delete the account?"
Well, if there is still the setup "do not delete accounts with G/L-entries after this date", it would be possible to adapt the Setup temporarily and delete the account. Though i personally would not do that, because then you have at least 2 G/L-Entries without account-number. And that could lead to questions in an financial Audit.
@Frederik Tanghe: thanks for your comments and your idea. :-)
Kind regards,
Birgit
The Conditional Access feature is an absolute must for any business pushing their financial data in to BC SaaS. It will be the case that customers who require control over SaaS application access for compliance will not be able to go ahead with BC SaaS. Please add this to the product roadmap.
This was quite a shock to us that there is no RTE shipped with the product nor any 3rd party offerings available on AppSource to close this important gap.
I know it is under review but when will a statement be shared about ETA for a solution. I see new RTE available https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/rich-text-editor-control and in the announcement it probably over-promise by this statement "We’re pleased to announce the release of the rich text editor (RTE) control, which can be used for any multi-line or single-line text field across Dynamics 365" - see https://powerapps.microsoft.com/en-us/blog/announcing-the-rich-text-editor-rte-control/
Microsoft please provide a statement of your plans for addressing this and others please share any solutions you have custom build if possible..