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
  • What can and can not be changed/deleted BEFORE publishing?
  • What can and can not be changed/deleted AFTER publishing?
  • Which data type should I use for which attribute?
  • Do I need to define attributes like Thing or Timestamp as well?
  • The messages sent include all attributes defined in the event schema but the messages are put into "invalid messages". Why?

Was this helpful?

  1. SF Platform
  2. Event Schema Management

FAQ and Troubleshooting

What can and can not be changed/deleted BEFORE publishing?

You can change and delete everything except the schema can not be deleted.

What can and can not be changed/deleted AFTER publishing?

You can change the name of the schema or of the attribute. You can also change the unit of an attribute. You can not change the key of a schema or attribute. You can not also change the data type or the decimals of an attribute.

Which data type should I use for which attribute?

  • String for text or single characters (variable unlimited length).

  • Boolean for true/false values.

  • Long, Integer (64 bit/32 bit) for signed and unsigned integers.

  • Double (64 bit) floating-point number for representation of decimals.

  • Timestamp for UNIX timestamps in milliseconds.

  • Time is not used anymore (deprecated).

  • None is not used anymore (deprecated).

All columns are also allowed to have NULL entries.

Do I need to define attributes like Thing or Timestamp as well?

No, the Thing and Timestamp columns are metadata. Every schema automatically has all metadata columns, which are: Id, Inserted, Size, Thing, Timestamp, Type.

The messages sent include all attributes defined in the event schema but the messages are put into "invalid messages". Why?

This could have several different reasons.

  1. Any value in the message is of the wrong data type

  2. Any value in the message includes an unexpected symbol

  3. There are some additional attributes that are not defined in the event schema

PreviousImporting a Event SchemaNextVirtual Events

Last updated 2 years ago

Was this helpful?