# CRUD Logging in Appfarm **URL:** \ **Category:** Ask the community\ **Created:** [July 4, 2024, 8:47am UTC](https://community.appfarm.io/t/crud-logging-in-appfarm/1311 "2024-07-04T08:47:21Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Malin](https://dub1.discourse-cdn.com/flex013/user_avatar/community.appfarm.io/malin/32/1634_2.png) [@Malin](https://community.appfarm.io/u/Malin)\ **Post date:** [July 4, 2024, 10:42am UTC](https://community.appfarm.io/t/crud-logging-in-appfarm/1311/2 "2024-07-04T10:42:00Z")
Hello, A similar question was asked about a week ago, and Kristian provided some information about built-in audit trail being on our roadmap. He also suggested a temporary implementation solution. You can read more about it here: > [@Audit trail on Object Class](https://community.appfarm.io/t/audit-trail-on-object-class/1283/2): > > Hello! Built-in Audit trail is on the roadmap, and will be a very nice feature (together with more support for listening to delete, update and create events on object classes, enabling a more event-driven architecture). Until then, I have a quite simple suggestion, that may be implemented. An action taking one (or more) string parameters as input. In this case, just a string that is indented to hold the new value of all changed properties. The action should create the audit log entry to be s… Hope this helps! / Malin --- _[View the full topic](https://community.appfarm.io/t/crud-logging-in-appfarm/1311)._