Custom Bitrix24 Filters: Development for Business Needs

Imagine: a manager needs to see deals where the total payments in the last 30 days are less than 50% of the deal amount. Or companies that have at least one deal at the 'Negotiation' stage with an amount > 1,000,000. The standard Bitrix24 filter cannot aggregate data from linked entities or execute subqueries. We develop custom Bitrix24 filters that solve these tasks—from aggregate filtering to 1C integration. We'll assess your project in 1 day, just reach out.

Our custom Bitrix24 filter development focuses on aggregate filtering, linked entity filtering, and complex CRM queries using the Bitrix24 REST API. This enables advanced reports and presets not available out of the box.

How the Standard Filter in Bitrix24 Works

In Bitrix24, the JS component BX.Main.Filter is responsible for filtering. It renders the panel, collects user input, and passes it to the backend handler. In the self-hosted version, the filter operates with ORM classes: \Bitrix\Crm\DealTable, \Bitrix\Crm\ContactTable. Each field maps to an ORM entity column. In the cloud version, filtering goes through the REST API—the filter parameter in methods like crm.deal.list, crm.item.list. Supported operators: =, !, <, >, <=, >=, %, array of values (IN). Not supported: grouping of AND/OR conditions at the filter level, aggregate functions, subqueries.

Why the Standard Filter Is Not Enough

Business processes require selection by metrics: "overdue more than 7 days", "clients with no activity for a month", "deals with accounts receivable in 1C". Without a custom filter, managers manually export data to Excel or spend hours on batch requests. A custom filter automates this work and reduces search time to seconds.

Architecture of a Custom Filter

A custom filter is a REST application with three layers:

1. Filter UI—your interface in an iframe (placement LEFT_MENU or CRM_*_LIST_TOOLBAR). The user sets parameters: period, amount threshold, entity type.

2. Backend handler—your server that accepts parameters, executes a complex query, and returns a list of IDs of matching items.

3. Result display—filtered data is shown in a custom list or passed back to the standard list via a preset filter.

Comparison of Filtering Approaches

A custom filter is up to 50 times faster than the standard one on large volumes.

HowTo: Filtering by Aggregates in Bitrix24

Follow these steps to implement a custom aggregate filter:

1. Collect data: Retrieve active deals via crm.deal.list with filter STAGE_SEMANTIC_ID=P. For each deal, fetch product items and payment history via crm.timeline.list or a custom field with payment amounts.

2. Perform backend aggregation: On your server, calculate payment_percentage = total_payments_30days / deal_amount * 100. If payment_percentage < 50, include the deal in the result set.

3. Cache results: Store the result in Redis with a TTL of 15–30 minutes to avoid repeated calculations on subsequent filter requests.

4. Display filtered IDs: Pass the list of filtered deal IDs to the UI or form a preset filter ID in the standard list using BX24.openPath('/crm/deal/list/?apply_filter=Y&ID[]=' + filteredIds.join('&ID[]=')).

This approach leverages server-side aggregation and incremental cache updates via webhooks (onCrmDealUpdate) for optimal performance. By using denormalization and materialized views, we achieve sub-second response times even on 10,000+ records.

Filtering by Linked Entities

Scenario: find companies that have at least one deal at the "Negotiation" stage with amount > 1,000,000. In the standard company filter, there are no deal fields. Solution: 1) request crm.deal.list with filter by stage and amount → get COMPANY_ID; 2) unique IDs → array for company filter; 3) request crm.company.list with filter: {ID: uniqueCompanyIds}. On the backend, this is a single SQL query with JOIN; via REST, it's a chain of 2–3 requests.

Custom Filter Presets

Presets save frequently used conditions: "Overdue > 7 days", "VIP clients with no activity", "Deals without tasks". The REST API has no method for programmatically creating standard filter presets, so we implement a custom UI with buttons:

var presets = {
    overdue_7: {'>DATE_CLOSE': formatDate(-7), 'STAGE_SEMANTIC_ID': 'P'},
    vip_inactive: {'UF_CRM_VIP': 1, '<DATE_MODIFY': formatDate(-30)},
    no_tasks: {} // server logic
};
function applyPreset(name) {
    loadFilteredData(presets[name]);
}

The "Deals without tasks" preset requires a batch request tasks.task.list with filter UF_CRM_TASK for each deal—solved with server-side aggregation.

Performance and Limits

The REST API limits: 2 requests per second, 50 commands per batch. For a filter on 10,000 deals:

Self-Hosted Version: Filters via ORM

In a self-hosted Bitrix24, a custom filter is implemented at the PHP level—extending the standard filter with new fields via the onBuildFilterFields event. The onBuildFilterQuery handler modifies the SQL query. This is more performant than REST but requires server access.

What's Included in the Work

• Analytics: studying business logic and filtering requirements.
• Design: architecture of UI/backend, caching scheme.
• Development: server-side logic, integration with REST API / ORM, implementation of presets.
• Testing: load testing on your data, selection accuracy verification.
• Documentation: description of filters, admin manual.
• Support: 1 month after delivery—revisions and consultations.

Timelines range from 5 to 20 days depending on complexity. We have 10+ years of experience in Bitrix24 and certified specialists—we guarantee quality and adherence to deadlines. Without a custom filter, you waste significant time on manual processing—development pays off within a few months. A typical investment of $1,000–$5,000 eliminates $500/month in manual labor, yielding ROI in 2–10 months. This custom filter investment of $2,000 typically saves $500 each month, resulting in an ROI of 4 months. This enables building complex Bitrix24 reports unavailable with standard tools. Contact us for a project assessment. Get a consultation.

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.