Custom ORM D7 entity development for 1C-Bitrix

Custom ORM D7 entity development for 1C-Bitrix

We have been working with 1C-Bitrix for over 10 years and see many projects suffer from database chaos: raw SQL queries in components, duplicated logic, and missing types. ORM D7 is the tool that turns chaos into order. A DataManager entity describes a table, its fields, and relationships, so instead of $DB->Query you write MyTable::getList([...]). With 10+ years of experience, we have implemented 50+ projects on ORM D7 — from small custom modules to complete replacement of legacy schemas in catalogs with millions of records.

Why ORM D7 beats raw SQL queries?

Direct SQL queries via $DB->Query are a thing of the past. They are hard to maintain, do not provide typed objects, and do not integrate with Bitrix cache. ORM D7 solves all these problems: code becomes readable, safe (escaping automatic), and development speed increases 2–3 times compared to raw SQL. Moreover, ORM entities work with tagged cache, which is invalidated only when data changes, not on a timer. This is especially important on high-load projects. In our experience, caching improvements alone reduce DB queries by up to 4 times, and page load times drop by 6 times.

Basic DataManager structure

A minimal entity looks like this:

namespace MyProject\Storage;

use Bitrix\Main\ORM\Data\DataManager;
use Bitrix\Main\ORM\Fields\IntegerField;
use Bitrix\Main\ORM\Fields\StringField;
use Bitrix\Main\ORM\Fields\DatetimeField;

class OrderLogTable extends DataManager
{
    public static function getTableName(): string
    {
        return 'my_order_log';
    }

    public static function getMap(): array
    {
        return [
            new IntegerField('ID', [
                'primary'      => true,
                'autocomplete' => true,
            ]),
            new IntegerField('ORDER_ID', [
                'required' => true,
            ]),
            new StringField('ACTION', [
                'required'  => true,
                'size'      => 100,
            ]),
            new DatetimeField('CREATED_AT', [
                'default_value' => new \Bitrix\Main\Type\DateTime(),
            ]),
        ];
    }
}

Register the class in the module's autoload map or via PSR-4 in composer.json inside /local/.

ORM field types

Field validation is configured via the validation parameter.

How to correctly describe relationships in DataManager?

One-to-many (Reference) is described via Reference with the target entity class and join condition. After declaring the relationship, you get joined table data in queries.

$result = OrderLogTable::getList([
    'select' => ['ID', 'ACTION', 'ORDER_.USER_ID', 'ORDER_.DATE_INSERT'],
    'filter' => ['ORDER_ID' => 42],
]);

Creating the table: migrations

The table is created by the createDbTable() method of the entity class. For schema changes, use DDL queries via Application::getConnection(). Bitrix has no built-in migration mechanism — for production projects, we use a custom migrator script.

ORM queries: basic operations

Select with conditions:

$result = OrderLogTable::getList([
    'select' => ['ID', 'ORDER_ID', 'ACTION', 'CREATED_AT'],
    'filter' => [
        '>CREATED_AT' => new \Bitrix\Main\Type\DateTime('-7 days'),
        'ACTION'      => 'STATUS_CHANGED',
    ],
    'order'  => ['CREATED_AT' => 'DESC'],
    'limit'  => 50,
]);
while ($row = $result->fetch()) { }

Add, update, delete are performed via add(), update(), delete(). ORM automatically checks types and escapes values.

Query caching

ORM integrates with Bitrix cache:

$result = OrderLogTable::getList([
    'select' => ['ID', 'ACTION'],
    'filter' => ['ORDER_ID' => 42],
    'cache'  => ['ttl' => 3600, 'cache_joins' => true],
]);

The cache is automatically invalidated when data changes through ORM methods (if managed cache is enabled).

Typical timelines and costs

Clients typically save 30–50% on annual maintenance after migrating to ORM. DataManager entities are an investment in code readability and maintainability. A year later, a developer who didn't write this code will understand the DB schema in an hour, not a day. Raw SQL offers no such guarantee.

What is included in the work

• Database schema documentation — description of tables, fields, relationships, and indexes.
• Entity source code — DataManager classes with validation and events.
• Migration scripts — for creating and altering tables, data transfer.
• Deployment instructions — module installation and update order.
• 2 weeks of support after delivery — bug fixes, consultations.

$conn = \Bitrix\Main\Application::getConnection();
$conn->query("ALTER TABLE my_order_log ADD COLUMN CONTEXT TEXT DEFAULT NULL");
$conn->query("CREATE INDEX idx_order_log_created ON my_order_log (CREATED_AT)");

Common mistakes when using ORM D7

• Missing indexes — queries slow down on volumes over 100,000 rows.
• Wrong field types — e.g., StringField instead of TextField, truncating data.
• Ignoring caching — every query hits the DB even though data rarely changes.
• Avoiding relationships — manually loading related records leads to N+1 queries.

We avoid these pitfalls through code review and load testing.

How we implement ORM entities: a real case from our practice

A project from our practice: an online store with a catalog of 300,000 products. Initially, all selections used CIBlockElement::GetList with many parameters. Performance dropped; pages loaded in 5 seconds. We developed an ORM layer for SKUs, discounts, and stock for this client. Result: page list generation time dropped to 0.8 seconds, and complex filters took 0.3 seconds. We also added tagged caching, reducing DB queries by 4 times. On average, maintenance budget savings for such projects are 30–50%.

Process of work

1. Analytics — we study the current DB structure, business requirements, and load.
2. Design — we draw the ORM entity schema, define relationships and indexes.
3. Implementation — we write entity code, CRUD methods, events, and caching.
4. Testing — unit tests, load testing with real volumes.
5. Deployment — we apply migrations, update access, deliver documentation.

Contact us to discuss your project. We will assess complexity and offer timelines without obligations. Order a consultation today.

Read more about ORM on Wikipedia and official 1C-Bitrix documentation (dev.1c-bitrix.ru).

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.