Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • Agile
      • Agile Webspace
      • Everything Agile
        • The Agile Manifesto
        • Best Practices
        • Retro Recipes
      • Methodologies
        • The Scrum Framework
        • Kanban
        • Extreme Programming
      • Roles
        • The Product Owner
        • The Agile Coach
        • The Quality & UX Coach (QX)
    • DataMiner DevOps Professional Program
      • About the DevOps Program
      • DataMiner DevOps Support
  • Downloads
  • More
    • DataMiner Releases & Updates
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

Parameter HistorySet – DateTime.Kind interpretation

Solved4.42K views1st September 2022historyset protocol
3
Thomas Cauwelier [SLC] [DevOps Advocate]1.50K 25th August 2022 0 Comments

Hi,

When performing HistorySets in a connector, how does the DateTime argument get interpreted?

Is the DateTime.Kind property considered, or does it see the value always as UTC or Local time?
If it considers the Kind property, how does it get interpreted when it is Unspecified?

Related documentation:
https://docs.dataminer.services/develop/devguide/Connector/Howto/How_to_use_history_sets_on_a_protocol_parameter.html#perform-the-history-sets

Thomas Cauwelier [SLC] [DevOps Advocate] Selected answer as best 30th August 2022

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
3
Thomas Cauwelier [SLC] [DevOps Advocate]1.50K Posted 30th August 2022 0 Comments

I tested all possible combinations.
Here are the results:

When DateTime.Kind is Local, it is properly handled as local server time.
When DateTime.Kind is Utc, it is properly handled as UTC.
When DateTime.Kind is Unspecified, it is handled as local server time.

Edit:

This is the behavior from 10.1.0 (CU18), 10.2.0 (CU6), 10.2.9 onwards.

Older DataMiner versions do not respect the Kind property of the DateTime and instead treat all timestamps as local time.

Edit:

Methods that do not have a DateTime timeInfo argument (like NotifyProtocol or AddRow) also do not respect the Kind property, even on later DataMiner versions.

So it is best to always use local time because it will always work regardless of version or method used.

Thomas Cauwelier [SLC] [DevOps Advocate] Edited answer 1st September 2022
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs