15,435
Hi
We like to log changes in a few fields in BC (mainly in SO /Quote). What is the best method here? What is the impact on performance (SaaS version)
I know I can either use "Change Log" or "Field Monitoring" but I am not sure which one is better? is it any other method available?
Also, in general what is the impact on performance and how we can eliminate such an impact?
Thanks
We have a customisation on Sales Order and Purchase Order subform. Together with activating change log on sales line for specific price and quantity fields. We have not seen an impact on performance, but we only have an average of 3 line items for per sales order and purchase order. The customisation adds an action on line that filters against that specific line record to see if there is any history of changes and has a nice hour glass icon. It's part of a very large customisation we do in house. If you have a partner I'd ask them, if you can do it yourself I'm happy to share code.
Hi RustyAustralis
Thank you so much for your help. What you described sounds like a good plan. Can you please provide more info? Do you mean you have a customization in SO that every time certain fields change it creates history for those fields?
Thanks
I customised our tenant with a history action on sales and purchase order lines that shows any changes in quantity and pricing. Invaluable given there is no undo and changes are made after every field is validated. Our people love it and it’s simple to do.
Hi Josh
Thank you for your response. We have about 20 "custom fields" in each SO that collect sensitive data. We need to have a log history for those fields. We tried "log field" but only keeps the last change. Do you know if "log field" can be designed to keep the history of change?
Also, I know you wrote a lot about Power Automation. Is it anyway that we can use Power Automation to create a log in a different system (let say Azure or Excel)?
Thanks
Hello, you are welcome. I think that webhooks has probably more of a performance overhead because they send out a message to an external system and will expect a reply back, while Change Log happens entirely inside of BC.
Hi Lars
Thank you for great information. Those are great tips.
I did not know about webhook. Sounds like a good method. Do you know if Webhook also cause performance issue or not?
Thanks again
For tables like the Sales Header and Sales Line you might want to consider what fields need monitoring and why. I'd assume it is prices and discount. If so why not have a dedicated field that tracks this on the sales line table instead - much more readable than the change log. You can then pull a report to determine this. If you do opt for standard change log then you will want to consider data retention policies to keep the change log in a readable state: docs.microsoft.com/.../admin-data-retention-policies
Hi,
In my opinion, I think that Change Log is probably the best designed for this purpose, so that's the way I would go. It will of course cost a bit of performance, how much is impossible to say, but it is easy to turn on and off, so I would just give it a try, and see if users start complaining about performance.
You ask for other methods, and there I can mention Webhooks. You can subscribe to a table-change, and then the webhook sends a message, but I would only go that way if you also want to log changes in a different system too. More about webhooks here:
docs.microsoft.com/.../dynamics-subscriptions
And I am sure there are many more methods. In short, my suggestion is to try out Change Log, most likely that does exactly what you need.
#1
André Arnaud de Cal...
292,892
Super User 2025 Season 1
#2
Martin Dráb
231,772
Most Valuable Professional
#3
nmaenpaa
101,156
Moderator
Share
Report
All responses (
Answers (
