Drawbacks of Standard Reports in Bitrix24

9 April 2017

next article

Middle back-end developer

Drawbacks of Standard Reports in Bitrix24

When dealing with CRM entities, we might need to create different variations of reports. Bitrix24 provides a constructor with various types of reports and graphs. Though, there can be some drawbacks observed, which limit task implementation. In this article, we will discuss the problems which might occur when using reports constructors.

Example 1 – non-standard report “Scheduling lead quantities in different regions”

In this case, we have a base of leads for which we use a “Region” field. On the ground of this field, we need to build a graph which would show the percentage of leads in each region. The settings for the report under consideration are presented in figure 1.

Figure 1 – Report Settings

First, you need to choose a lead ID as a field for the quantity computation. You will assign it a “Unique quantity” value. Then, we are to add the rest of the fields which we want to be presented in our table report. And we will point out that we need a pie chart for this report. Choose “Region” field as an argument, and quantity of leads in the region as a value for this argument. The result is shown in figure 2.

Figure 2. – Report Graph

At first glance, everything seems to be OK. We’ve got a complex graph which displays accurate information about all our leads. In the lower part, the numeric value of leads in each region is displayed. But if we consider the case in detail, we will see there is a difference in the total number of leads in the graph and their real number in CRM. After addressing Bitrix24 technical support team, it turned out that the graph does not work properly if the report contains more than 2000 records. The rest of the data is eliminated. So, it is necessary to minimize the number of leads operated in the report to make the graph valid.

There is one more drawback in the graph. In figure 2, you can see an “Others” option. But there is no such value in a “Region” field. When asked why all the data was not presented in the graph, the support team answered that the data cannot fit in, thus, they are automatically replaced to an “Others” segment. It is quite possible to fail to see the percentage of all values because they just don’t fit in. Again, we need to cut down operated data.

The conclusion can be made that today, Bitrix24 is not suitable for processing large data. In the wake of complaints, improvement applications were sent to the development department with the request to fix these problems in the forthcoming upgrades.

Example 2 – standard Bitrix24 report “Leads by managers distribution”

In this example, we will analyze a reporting filter “Report for the period”. On the top right corner of figure 3, you can see a report filter with a field for reporting period. And it can be observed in more detail in figure 4.

Figure 3. – “Leads by Managers Distribution”

Figure 4. – Report Filter in Detail

This value chooses leads more extensively than only for a selected time period. Indeed, it will include all the elements which were in work during the chosen period. Those which were created within this interval, finished, changed, as well as those which were unfinished or not processed. To build a report covering leads which entered during the period under consideration, you need to put the finishing touches to the filter as it is shown in figure 5.

Figure 5. – Advanced Setting for Report Filter

At present, these are the main problems with standard reports that I have encountered.

Similar articles

Apply for a consultation

We will reach out to within 10 minutes