Skip to content

History logging can't be enabled for a custom field/attribute added to an out-of-the-box entity, even though the equivalent worked in the on-premise product.

Answer

This is a confirmed platform limitation, not a configuration step you're missing — history logging on custom-field tables isn't currently supported the way it was for custom attributes in the on-premise product, so don't spend time hunting for a missing configuration entry; track official release notes if this matters for your rollout.

← Browse Platform, Aurena, and customization questions