Using IntelliFront BI
      Back to home
      1. Knowledge Base
      2. IntelliFront BI
      3. Using IntelliFront BI

      What data types are supported with IntelliFront Dashboards?

      The IntelliFront Dashboard supports data types primarily based on what the underlying data source provides (SQL, Excel, Object, EF, etc.).

      The IntelliFront Dashboard supports data types primarily based on what the underlying data source provides (SQL, Excel, Object, EF, etc.). It maps these data types into its own simplified internal types for visualization.

      Supported Data Types in DevExpress Dashboard

      Internally, the IntelliFront Dashboard uses these general data types for binding and visualization:

       
       

      Dashboard Data Type

       

      Description

       

      Common .NET or DB Types Mapped

       

      String

      Textual data for labels, categories, etc.

      string, varchar, nvarchar, char

      Numeric

      Any number used for metrics, values, KPIs

      int, long, decimal, float, double, numeric

      DateTime

      Time-based data for timelines, filtering, grouping

      DateTime, datetime, date, smalldatetime

      Boolean

      Used in filtering, conditions, visibility rules

      bool, bit

      GeoPoint / GeoData

      For map visualizations

      Typically from latitude/longitude or ISO/country/city fields

      Image / Binary

      Only in Image-type widgets or when bound explicitly

      byte[], Base64 strings
       
       

      How Dashboard Interprets These Types

      When you bind data in the dashboard:

      • The data source type determines the .NET type.

      • The dashboard runtime classifies it into one of the internal types above.

      • Certain visualizations (e.g. charts, grids, maps, gauges) support only compatible types.

      For example:

      • Cards & Gauges: Expect numeric values.

      • Pie/Bar Charts: Expect dimension (string/date) + measure (numeric).

      • Maps: Use GeoPoint or string-based region names (e.g. country).

      Notes by Data Source

      • SQL: Types like int, decimal, datetime, bit, etc., are mapped automatically.

      • Object Data Source: Based on property types of your objects.

      • Entity Framework: Uses EF's model metadata to infer types.

      • Excel / CSV: Parsed based on cell content, so it's best to format data consistently.

      Things to Watch Out For

      • Nullable types: Supported, but filters or KPIs might treat null as "empty".

      • Calculated Fields: You can create new fields using expressions that return numeric, string, or datetime.

      • Custom Visuals / Parameters: Can bind to string, number, or datetime—but not complex objects.