Experience Builder limitation: unable to create a default display range for bar charts

417
0
01-25-2023 07:55 AM
ScottHansen__MDP_
Occasional Contributor

In Web App Builder's infographics widget, I can create a bar chart to illustrate land use around a transit station, which may include 7+ unique land use categories or fields. Thanks to Web App Builders default display range option, this is possible. I attempted to recreate the same bar chart widget in Experience Builder, however, I am unable to and received the following message:

"Too many features. Bar charts with with three or more series are limited to 1,000 bars, or 100 bars per series. Choose a category field with fewer unique values or apply a filter to your data."

Experience Builder should implement the default display range feature available in Web App Builder, which includes options such as "automatic" or "all." Choosing "automatic" will display a horizontal scroll bar just above the bar chart, so that a user can select the number of stations to view in the chart. 

Web App Builders default display range options allow you to view a large number of data series by manipulating a horizontal scroll bar.Web App Builders default display range options allow you to view a large number of data series by manipulating a horizontal scroll bar.

A bar chart in Web App Builder's infographic widget, provides a horizontal scroll bar feature to allow user to view areas of interest.A bar chart in Web App Builder's infographic widget, provides a horizontal scroll bar feature to allow user to view areas of interest.

The "automatic" option under the default display range setting displays data according to the data sort. For this example, I choose an alphabetical sort, so Aberdeen is fist, followed by Addison Road-Seat Pleasant. If you choose 'all," the complete data series, or in my case, stations, would appear, but they would display as very thin/small lines in order to fit all of the stations data into the view. It is important to have a default display option, when filtering at the out-set is not appropriate.

0 Replies