For now, since the customer/partner cannot delete those entries, the data size of those entries are increasing day by day.
However, we can never delete those log entries with any permissions right now.
We would like a new feature to delete those change log entries in any ways.
For instance, if you want users not to delete those log entries, you should be able to restrict to do that based on user's permissions.
It would be great to consider the request.
Thank you.
Comments
I mean Table 17 G/L Entry.
> In the case of table 17 change log entries, the reason for not allowing the deletion is that, in case this logging is required by GAAP or company policy , deletion of the entries could mask entries not according to them. Do note that those entries can be deleted by a PTE if Change Log was enabled by mistake.
Why don't you allow their D365BC admins to choose whether they can delete it or not according to their country, company policy or stuff like that?
I assume there are many customers who did not know the deletion for the table was not allowed at all and already had enabled logging on the table17.
There is no announcement for this restriction currently.
At least those customers who already enabled logging on the table17 and want to delete change log entries for table17 now should be able to request Microsoft to delete the entries instead of them.
While there is no workaround to delete those entries, there should be a workaround other than PTE.
If PTE can help this out, please provide sample PTEs with codes.
It would be really helpful for a lot of customers.
Please reconsider this request.
Category: General
Business Central Team (administrator)
Thank you for your feedback. We need some more details to understand your suggestion better. Can you please help us by answering the following questions?