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
  • A data source column is not available to map on a certain attribute!
  • Where can I get information about the generated virtual events?
  • Why can't I change/delete the attributes or delete the virtual event?
  • I can not see the data which should have been generated by a virtual event!
  • What should I use the "run per thing" option for and why can't I use it for datasets?
  • What happens if I use the "run per thing" option and one of the script executions fails?

Was this helpful?

  1. SF Platform
  2. Virtual Events

FAQ and Troubleshooting

PreviousPermissions and Data AccessNextDetails modal for elements

Last updated 3 years ago

Was this helpful?

A data source column is not available to map on a certain attribute!

Data types of the data source column and the attribute need to match. In the drop-down, only columns with matching data types are shown.

Where can I get information about the generated virtual events?

The virtual events produce sf-messages, so you can get information on which virtual events got generated when with help of the sf-messages.

Why can't I change/delete the attributes or delete the virtual event?

In the actual version deleting attributes and virtual events is not possible. But you can change the name of attributes and virtual events.

I can not see the data which should have been generated by a virtual event!

If you do not have access to all things, it could be that the virtual events are related to a thing you do not have to, e.g. if you use a . Another reason could be that your data source had an error. If your data source had an error no virtual event will be written to the database.

What should I use the "run per thing" option for and why can't I use it for datasets?

In scripts, the imported datasets have a row limit of 1.000.000. If your virtual event calculates a benchmark for every individual machine you might exceed this limit. If you select "run per thing" the script will run separately for every thing selected in the global thing filter. Therefore you get a 1.000.000 row limit per thing, instead of having 1.000.000 rows in total.

For datasets there is no row limit, hence the option does not make sense.

What happens if I use the "run per thing" option and one of the script executions fails?

Using the "run per thing" option also makes the single script executions independent from each other. So if one execution fails no rows will be created for this virtual event execution, but if the executions of the other things are successful this data will be inserted into the database.

For common mistakes which can to errors in script see the script .

virtual thing
access
FAQ and Troubleshooting