You are here:
Present Data Effectively with Charts
Report chart appearance can be affected by negative values, very large or small numbers, custom summary formulas, and field-level security. Chart appearance can also change when you switch the report format or change groupings and blocks.
Required Editions
| Available in: Salesforce Classic and Lightning Experience |
| Available in: Essentials, Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
| Available in: Enhanced Folder Sharing |
- You can't have more than 250 groups or 4,000 values in a chart. If you see an error message saying that your chart has too many groups or values to plot, adjust the report filters to reduce the number. In combination charts, all groups and values count against the total.
- If you lose access to a field used in a chart, use another field in its place. If no other fields are available, record count is used.
- Decimal-place precision on charts isn’t customizable. Numeric and currency values round to two decimal places. Percentage values round to one decimal place.
- If numeric values are too large or too small, they’re shown in scientific notation. For example, the number 5,750,000,000 is displayed as 5.75E9; -0.0000000061 is displayed as -6.1E-9.
- Some charts may display shortened numbers with a unit symbol.
Symbol Unit Example K Thousand (10^3) 4K = 4,000 M Million (10^6) 4M = 4,000,000 B Billion (10^9) 4B = 4,000,000,000 T Trillion (10^12) 4T = 4,000,000,000,000 P Quadrillion (10^15) 4P = 4,000,000,000,000,000 X Quintillion (10^18) 4X= 4,000,000,000,000,000,000 Z Sextillion (10^21) 4Z = 4,000,000,000,000,000,000,000 Y Septillion (10^24) 4Y = 4,000,000,000,000,000,000,000,000 m Thousandth (10^-3) 4m = 0.004 μ Millionth (10^-6) 4μ = 0.000004 n Billionth (10^-9) 4n = 0.000000004 p Trillionth (10^-12) 4p = 0.000000000004 f Quadrillionth (10^-15) 4f = 0.000000000000004 a Quintillionth (10^-18) 4a = 0.000000000000000004 z Sextillionth (10^-21) 4z = 0.000000000000000000004 y Septillionth (10^-24) 4y = 0.000000000000000000000004 - Negative values are displayed on all line charts and bar and column charts.
In Salesforce Classic, negative values don't appear on pie, donut, and funnel charts. Groupings containing negative values appear in the legend, and negative values are reflected in the calculation of all summary values, including the total for donut charts.
In Lightning Experience, negative values appear on donut and funnel charts.
- When creating charts, it isn’t good practice to group by a field on a child object and then sum by a field on the parent object. On a donut chart, for example, it’s possible that the total shown doesn’t match the sum of the wedges.
- In Salesforce Classic, dashboard and report charts that display values from summary formulas display decimal places using your default currency setting instead of what you specified for the formula. For example, if the summary formula specifies zero decimal places, no decimal places appear in columns, but chart values show the number of decimal places specified for your default currency (usually two decimal places). This limit applies to currencies, numbers, and percentages.
- With joined reports, summary field names contain both the field name and the block name. For example, if you’ve summarized the Amount field in Block 1, it appears as Block 1 — Sum of Amount in the Chart Editor. A cross-block or standard custom summary formula contains the block name when the formula is included in multiple blocks.
-
When a report already has a chart, changing the report format or removing blocks, groupings, or summary fields has the impacts described in this table.
When you make this change ... The effect is ... Switch format from summary, matrix, or joined to tabular All charts are removed from the report. Switch format from summary to matrix The first summary grouping becomes the first row grouping. The second becomes the first column grouping. The third becomes the second row grouping. The chart is unchanged. Switch format from matrix to summary The first row grouping becomes the first summary grouping. The second row grouping becomes the third summary grouping. The first column grouping becomes the second summary grouping. The second column grouping is removed. If the chart used the second column grouping, that grouping is replaced by the first available summary field that’s not already used in the chart. Switch format from summary or matrix to joined The existing report becomes the first block and the chart remains in the report.
If the matrix report used the second column grouping, that grouping is replaced by the first available summary field that’s not already used in the chart.
If the summary or matrix report included a grouping from a bucket field, the grouping is replaced with the next available grouping not already used in the chart.
Switch format from joined to summary or matrix The first block becomes the report, and groupings and the chart are preserved. If the chart in the joined version contained summary fields from the first block, they remain in the chart in the summary report. Summaries from other blocks are removed from the chart. Remove a block containing a summary field from a joined report The summary field is replaced with the next available summary field. If no additional summary fields are available, the original field is replaced with the record count from the first remaining block. Removing all blocks from a report removes the chart completely. Remove a grouping used in the chart The grouping is replaced with the next available grouping. If all groupings are removed, the chart is removed as well. Groupings can be removed automatically when you add a report type to a joined report or if a field becomes unavailable, for example as a result of field-level security. Remove a summary field used in the chart (including custom and cross-block summaries) The summary field is replaced with the next available summary field. If no additional summary fields are available, the field is replaced with the record count for either the report or the first block. Summary fields can be removed automatically, for example as a result of field-level security or when the report format changes.
