bitrix-orm

To model data using Bitrix D7 ORM, you extend the DataManager class to scaffold a Table, define field types in the getMap method, and execute CRUD operations. This replaces ad-hoc SQL by providing a structured, type-safe data layer for your modules.

Defining relationships in a Bitrix D7 ORM table map requires using the Reference field type within your getMap configuration. This establishes structured links between entities, allowing you to fetch related data seamlessly via fetchObject and fetchCollection instead of writing manual SQL joins.

Querying and fetching objects using Bitrix D7 DataManager involves utilizing standard ORM helpers and runtime query capabilities. You call query methods on your Table class to filter records, then use fetchObject or fetchCollection to retrieve type-safe entity instances directly from the database.

Yes, you can handle table events for add, update, and delete operations in Bitrix D7 ORM. The framework supports event handlers within your Table classes, allowing you to trigger custom logic automatically whenever data modifications occur through the DataManager interface.

Yes, Bitrix D7 ORM supports generating IDE annotations for table entities. After extending DataManager and defining your map, you can run the ORM tooling to automatically generate annotations, ensuring your development environment recognizes the type-safe properties of your data models.

You should use Bitrix D7 ORM over direct database queries when you need a structured, type-safe data layer across DataManager and Table classes. It is ideal for managing complex entities, relationships, and CRUD operations, replacing ad-hoc SQL with maintainable, fluent configuration.