Senseforce 2.0 Manual
  • Welcome to Senseforce 2.0
  • SF MQTT API
  • SF Edge
    • Edge Package Overview
    • Edge Installation
      • Using the SF Edge Service installer in command shell
      • Headless SF Edge Servie execution
    • Edge Configuration
      • Which Plugins to load (appsettings.xml)
      • Edge Data Routing (EventDefinition.xml)
      • OTA configuration (otasettings.xml)
      • Edge Logging
      • Input plugins
        • SQL Plugin
        • SQLite Plugin
        • OPC UA Plugin
          • OPC UA server browser
        • SIEMENS S7/SINUMERIK Plugin
          • Creating connection definition file
        • S7 Plugin
        • REST Plugin
        • TCP Listener Plugin
        • XML File Parsing Plugin
        • Heidenhain Plugin
      • Output Plugins
        • MQTT Plugin
        • SQLite Plugin
    • Edge Compute plugins
      • Creating compute plugins
      • Using compute plugins
  • SF Edge Asset Management
    • Edge version repository
  • SF Platform
    • Navigation
      • Overview Screen
    • Dataset Builder
      • Filters, Aggregations and Groupings
      • Functions of the Formula Editor
      • Additional Settings
      • Special Events
      • FAQ and Troubleshooting
    • Script Editor
      • Details of the Script Editor
      • Installed Packages
      • Working with Timestamps
        • Working with Timestamps in Python
        • Working with Timestamps in R
      • FAQ and Troubleshooting
    • Widgets
      • Text
      • Headline
      • Image
      • Progress Bar & Gauge Chart
      • Table
      • Map
      • Line, Bar, Scatter and Area Chart
      • Pie Chart
      • Gantt Chart
      • Histogram
      • Overview
      • Log
      • Default colors and color conditions
      • FAQ and Troubleshooting
    • Dashboards
      • Dashboard Filters
      • Favorites
      • Data Drilldown & Widget Interaction
      • Editing multiple dashboard widgets
      • Time Zones
      • Synchronized Zooming
      • Sharable Dashboard URL
      • Multi-chart layout options
      • Default sort for table widgets
      • Releases
      • Reporting
      • FAQ and Troubleshooting
      • Applying zoom to global timestamp filter
      • Optimise the layout for different devices
    • Machine Master Data
      • Dimensions
      • Instances
      • Things
      • Use Case
      • FAQ and Troubleshooting
    • Automation
      • Trigger
      • Scheduling overview
      • Actions
      • Test your Automation
      • Zapier integration (necessary internal steps)
      • Zapier integration
      • Subscriptions
      • FAQ and Troubleshooting
    • Event Schema Management
      • Importing a Event Schema
      • FAQ and Troubleshooting
    • Virtual Events
      • Creating a Virtual Event
      • Scheduling Overview
      • Permissions and Data Access
      • FAQ and Troubleshooting
    • Details modal for elements
    • Copy / Duplicate elements
    • Whitelabeling
    • Edge Device Management
    • Element History
    • Public API
      • Get your access token
      • Endpoints
      • Debugging scripts
      • FAQ and Troubleshooting
    • User & Group Management
      • FAQ and Troubleshooting
    • Active Directory & SSO Setup
Powered by GitBook
On this page

Was this helpful?

  1. SF Platform
  2. Event Schema Management

Importing a Event Schema

PreviousEvent Schema ManagementNextFAQ and Troubleshooting

Last updated 3 years ago

Was this helpful?

If you do not want to set up your event schemas manually you can also use the "Import Schema" function.

To create a schema via import you just need to create a text file and save it with the file extension .csv. Within the text file, you need to apply some rules, such that your definition is interpreted correctly. An example for a valid .csv would be,

Key;Name;Datatype;Units;Decimals
BW_0;Wind Speed;long;km/h;
BW_1;Day of Week;string;-;

The first line needs to be the same in every definition. In this example the following lines define attributes with keys BW_0/BW_1, names "Wind Speed"/"Day of Week", data types long/string, units km/h/- and no decimals.

Does and Don'ts

  • The keys are not allowed to contain whitespace characters.

  • The units need to contain a non-whitespace character (if you do not want to assign a unit use "-").

  • Allowed keywords for the data types are string, boolean, long, double, timestamp, and integer. The datatype definition is case insensitive. So the can be written in upper or lower case.

  • If you use the data type double you need to assign a number of decimals (for every other data type this is ignored).

  • The keys are not allowed to be equal to "id", "inserted", "size", "thing", "timestamp" or "type". Because they are always added automatically to each schema and therefore these keys are already used.

Enter the Event Schema Management, then click "Import Schema".