Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Load Events Using LoadRecord and LoadRecords

Geo SCADA Knowledge Base

Access vast amounts of technical know-how and pro tips from our community of Geo SCADA experts.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Geo SCADA Knowledge Base
  • Load Events Using LoadRecord and LoadRecords
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Labels
Top Labels
  • Alphabetical
  • database 32
  • Web Server and Client 31
  • WebX 19
  • Request Form 18
  • Lists, Events & Alarms 16
  • ViewX 15
  • Application Programming 12
  • Setup 12
  • Telemetry 8
  • Events & Alarms 7
  • Lists 7
  • Mimic Graphics 7
  • Downloads 6
  • Support 5
  • IoT 5
  • SCADA 5
  • Geo SCADA Expert 5
  • Drivers and Communications 4
  • Security 4
  • DNP 3 3
  • IEC 61131-3 Logic 3
  • Trends and Historian 2
  • Virtual ViewX 2
  • Geo Scada 1
  • ClearSCADA 1
  • Templates and Instances 1
  • Releases 1
  • Maps and GIS 1
  • Mobile 1
  • Architectures 1
  • Tools & Resources 1
  • Privacy Policy 1
  • OPC-UA 1
  • Previous
  • 1 of 4
  • Next
Latest Blog Posts
  • OPC UA - Driver and Server
  • Requirements for Generating a Valid OPC UA Server Certificate
  • Load Events Using LoadRecord and LoadRecords
  • Geo SCADA Embedded Component Licenses
  • Geo SCADA 2023 Known Issues
Related Products
product field
Schneider Electric
EcoStruxure™ Geo SCADA Expert

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
AdamWoodland
AdamWoodland Schneider Alumni (Retired)
Schneider Alumni (Retired)
‎2024-03-25 01:52 AM
0 Likes
0
723
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

‎2024-03-25 01:52 AM

Load Events Using LoadRecord and LoadRecords

Originally published on Geo SCADA Knowledge Base by AdamWoodland | March 25, 2024 09:52 AM

📖 Home   Back  

 

Overview

Event data can be loaded into the Geo SCADA historian using some database methods:

  • LoadRecord - One event at a time with any freeform/custom text as the event message
  • LoadRecords - Multiple events at a time, supporting multiple objects at the same time, with any freeform/custom text for the event message

The only difference in parameters between these two methods are LoadRecords takes an array of values (even if an array size of 1) whereas LoadRecord just takes a singular value from each parameter.

LoadEncodedRecord and LoadEncodedRecords also exist, the only difference with these is the message parameter for these two methods must be a defined encoded message that allows backend support for internationalisation. The encoded message can be extracted from CDBEventJournal using the EncodedMessage column. Using the encoded message is typically better for moving events between two Geo SCADA systems, whereas the non-encoded messages will be necessary when bringing in event data from other systems.

 

Parameters

Parameter Maps to CDBEventJournal Column Details
Timestamp (Time) RecordTime The time in UTC of the event message for the source of the event (e.g. timestamp from RTU if event is originally sourced from an RTU)
ClassName (String) Category The event category name of the event based on the category name in the table DBEventCategoryDef, not the friendly description seen by users in CDBEventJournal (do a SQL JOIN between those tables if necessary to extract in one go)
ObjectId (Long) Id / Source The valid database object id that the event is to be loaded into
Severity (Long) Severity / SeverityDesc / SeverityValue Database severity between 1 and 1000, ideally should match a valid severity on the target system but will round down to the nearest severity if not matched. Will error if 0 is used.
OPCType (Long) None Bitmask for the OPC-AE event type:

 Bit 1 - Simple

 Bit 2 - Tracking

 Bit 3 - Condition

Bitmask cannot be 0, so unless you specifically need to set the event type suggest just using a value of 1 for the imported events

SCXType (Long) AlarmStateDesc

Shows the alarm state causing the event:

  1. Blank entry
  2. "Alarm Raised"
  3. "Alarm Cleared"
  4. "Alarm Accepted with Comment"
  5. "Alarm Accepted"
  6. "Alarm Removed with Comment"
  7. "Alarm Removed"
  8. "Alarm Disabled"
  9. "Alarm Enabled"
  10. "Alarm Response"
  11. "Alarm Unaccepted with Comment"
  12. "Alarm Unaccepted"
Message (String) Message / EncodedMessage The message shown for the event entry, see above for details on EncodedMessage. Cannot be blank.
UserName (String) User Can be any valid string, including blank.
SeqNo (Long) None Doesn't currently import anything, use Null/Nothing depending on your coding language. A new SeqNo will be generated by the server automatically
CommentNo (Long) None Use 0, no other value supported
ReceiptTime (Time) ReceiptTime The timestamp for the event that the server receives it, for the import typically the same as RecordTime or the current time depending on need
ClientAddress (String) ClientAddress

The IP address of the user that generated a source using string (dotted quads) or as 32-bit unsigned representation of the IP address.

Cannot be blank, use "0" for a blank entry in the event journal else provide a valid IP address

AreaOfInterest (Long) AreaOfInterest Use 0 for "World", else a valid Id for an AOI. Parameter still required if AOI is disabled on your system (just use 0 in this case)
SuppressionType (Byte) SuppressionDesc
  1. Blank entry
  2. "None"
  3. "Consequential"
  4. "Maintenance"

Doesn't cause any suppression to occur, just cosmetic.

 

📖 Home    Back  

Labels:
  • SCADA

  • Telemetry

  • Tags:
  • english
  • scada
  • SCADA app
  • SCADA software
  • SCADA tutorial
  • Telemetry and SCADA

Author

Biography

AdamWoodland

Link copied. Please paste this link to share this article on your social media post.

  • Back to Blog
  • Newer Article
  • Older Article
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of