In the process of using ShareCRM products, users will involve various mathematical operations, such as calculating the shipping price based on the official quotation and discount of the product.
The above-mentioned functions can be easily satisfied by using the calculation fields.
The calculation fields provided by ShareCRM can use different operators and functions to calculate according to different expected result values, and calculate the corresponding results in combination with parameters that meet the requirements (other fields or constants).
1. Calculation fields can support filtering on the data list page
Scene Description: In the sales order list, add two calculation fields, the contract start time and the contract remaining end time. The user wants to be able to filter these two fields in the data list.
- The data list page supports filtering calculation fields. Users can filter data through calculation fields as needed to better assist users in data filtering and viewing.
2. Statistics fields and calculation fields can be intercalculated
2.1 Scene Examples
Calculate the cost of a single product under the invoice product, and hope that the total cost can be counted in the invoice for profit analysis.
2.2 Logic Analysis
Statistics fields supports to count statistics fields and calculation fields on main bjects or related objects.
-
Example of use in specific business
Maybe many people still look at the picture above with blindfolded eyes, so let me give you a specific example of one of the points:
At the beginning, we mentioned that users hope to support profit analysis through our statistical capabilities. Now we can support it. How to configure it specifically? Another picture:
As can be seen from the figure above, originally we could only calculate the profit of each piece of detailed data through the calculation field, but after the statistical ability is improved, we support the calculation field of the master object to count the slave object, then the user can calculate the total profit on the master object analysis.
- Correction of the original wrong practice
3. Level Restrictions on Calculation/Statistics Intercalculation
In view of performance considerations, there are restrictions on the link level supported by calculation and statistics. For details, please refer to the following diagram:
3.1 Level Restrictions for Verification Initiated by [Calculation Fields]
-
Level Analysis:
-
Upper Level: main object or lookup object field
-
This Level: fields of this object
-
Lower Level: sub-object or related object fields
-
-
Notes:
-
"Related objects" refer to objects that lookup this object, for example: [sales order] lookup [account], then: [sales order] is the related object of [account]
-
It is recommended to view the level from the node that initiates the verification for easy understanding.
-
calculate--default–(only main)-statistics means that for the default value of the upward reference of the calculation field, only the default value field of the main object can refer to the statistics field of this object.
-
-
Example: Give an example of part of the above picture
- As shown in the figure above: If the node that initiates the verification is triggered from the calculation field of [Quotation], it will refer to the upper and lower level. When this "calculation field" has already referenced a "statistics field" in this object, then this "statistics field" cannot refer to the calculation field/statistics field in [Quotation Details], and can only refer to the default value of [Quotation Details].
3.2 Level Restrictions for Verification Initiated by [Statistics Fields]
- Please refer to the explanation and examples in "Level Restrictions for Verification Initiated by [Calculation Fields]" in 1.
3.3 Level Restrictions for Verification Initiated by [Default Value]
- Please refer to the explanation and examples in "Level Restrictions for Verification Initiated by [Calculation Fields]" in 1.
4. Configuration Page Prompt Message
When a scene that does not meet the rules is configured, the user will be prompted for the wrong configuration link. Here is a detailed explanation of the prompt message to help you understand.
-
Prompt Message: "The system does not support multi-level calculation/statistics intercalculation at the moment, you have configured [object name.field name->object name.field name->object name.field name] (-> stands for reference) ”
-
EXAMPLE EXPLANATION:
- When the "Store Credit" field has been configured in the [Invoice] to calculate the credit value under the related object [Store], if you add the "Discount Quota" field in the [Invoice] to refer to the "Store Credit" of this object ", the following error will be reported when the field is saved. It means that this link does not support configuration.
