1. Reports

1.1 Multi-timezone Analysis for Reports

• For organizations that have enabled multi-timezone support and whose BI feature flag includes multi-timezone analysis, new reports default to displaying data in the report creator’s personal timezone.
• Users can switch the report timezone. After switching, the report displays data according to the user-selected timezone.

1.2 Example 1

ShareCRM has three branches worldwide: Beijing Branch, New York Branch, and London Branch. Each branch lead needs to view and aggregate Sales Orders count and order amount for November 2022.
First step: Create a new report and select the International Sales Order object. Set Order Submission Time to This Month, and set Dept. to ShareCRM Beijing Branch. Drag in the fields Dept., Sales Order ID, and Order Amount. Set the timezone to UTC+8.

Second step: Group by Dept. Then set aggregation methods: set Sales Order ID to Count, and Order Amount to Sum. You will see the Beijing Branch’s order count and order amount for the month.

If the New York Branch lead wants to view their branch’s monthly orders and amounts, change the Dept. filter to ShareCRM New York Branch and set the timezone to New York (UTC-5). The London Branch follows the same steps.

1.3 Reports Using Business Occurrence Timezone

• If an object’s date/datetime field is configured as not following multi-timezone behavior, that field’s data does not change when the report timezone switches.

1.4 Example 2

ShareCRM has three branches worldwide: Beijing Branch, New York Branch, and London Branch. The corporate headquarters is in Beijing. The HQ lead needs to view all branches’ Sales Orders count and order amount for November 2022 at once.
First step: Mark the Order Payment Time field on the object as “does not follow multi-timezone” and lock the setting. This configuration means the field will always display the time recorded in the timezone where the business actually occurred. For example, if a payment recorded in UTC-5 has a payment time of 2022-11-11 15:30, every view will display that same timestamp regardless of viewer timezone. In the system this is defined as the Business Occurrence Timezone.

Second step: Create a new report and select the International Sales Order object. Set Order Payment Time to This Month and set Dept. to ShareCRM Beijing Branch, ShareCRM New York Branch, and ShareCRM London Branch. Drag in Dept., Sales Order ID, and Order Amount. Set the timezone to Business Occurrence Timezone.

Third step: Group by Dept. Then set aggregation methods: set Sales Order ID to Count, and Order Amount to Sum. You will see the order count and order amount for the month across branches.

2. Charts

2.1 Multi-timezone Analysis for Charts

• When creating a metric that aggregates by a date or datetime field that follows multi-timezone behavior, you can set a custom aggregation timezone. The metric aggregates and displays data according to that chosen timezone.
• When creating a chart, the chart’s default timezone is the viewer’s personal timezone. You can use metrics whose aggregation timezone matches the chart timezone.

2.2 Example 3

ShareCRM has three branches worldwide: Beijing Branch, New York Branch, and London Branch. Each branch lead needs to view and aggregate Sales Orders count and order amount for November 2022.
First step: Create a metric named “Beijing Branch Order Count.” Use the International Sales Order object and count unique Sales Order ID aggregated by Order Submission Time using UTC+8. Create other branch metrics similarly. When aggregating for a specific branch, choose the corresponding timezone.

Second step: For the chart, set dimensions to Dept. and Owner. Select metrics Beijing Branch Order Amount and Beijing Branch Order Count. Set data range Order Submission Time to This Month and Dept. to ShareCRM Beijing Branch. Set the chart timezone to UTC+8. Note: the metric picker only shows metrics whose aggregation timezone matches the chart timezone, metrics with no aggregation date, or metrics that do not follow multi-timezone behavior.

If the New York Branch lead needs to view their branch metrics, switch the chart timezone to UTC-5. The chart will clear all metrics; the metric list will then show only metrics aggregated in UTC-5, metrics without aggregation date, and metrics that do not follow multi-timezone. Add the appropriate metrics and configure the data range. London Branch follows the same procedure.

2.3 Charts Using Business Occurrence Timezone

• When creating a metric that aggregates by a date/datetime field configured as not following multi-timezone behavior, the metric’s timezone can only be set to Business Occurrence Timezone. The metric displays timestamps according to the timezone where the business actually occurred.
• Charts can switch to Business Occurrence Timezone and then use metrics defined with Business Occurrence Timezone.

2.4 Example 4

ShareCRM has three branches worldwide: Beijing Branch, New York Branch, and London Branch. The corporate headquarters is in Beijing. The HQ lead needs to view all branches’ Sales Orders count and order amount for November 2022.
First step: Create a metric named Order Count. Use the International Sales Order object and count unique Sales Order ID aggregated by Order Payment Time using Business Occurrence Timezone. When a chosen aggregation time field is configured as not following multi-timezone, the aggregation timezone defaults to Business Occurrence Timezone. See Example 1 for how to set a field to not follow multi-timezone.

Second step: Create a chart and set the timezone to Business Occurrence Timezone. The metric list then shows metrics that do not follow multi-timezone and metrics without an aggregation timezone. Add Dept. as a dimension and add metrics Order Count and Order Amount. Set data range Order Payment Time to This Month and Dept. to ShareCRM Beijing Branch, ShareCRM New York Branch, and ShareCRM London Branch. You can now view order counts and order amounts for all branches.

picture coming soon: