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
    • 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
    • YouTube Videos
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Agility
      • Learn more about 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)
      • Book your Agile Fundamentals training
      • Book you Kanban workshop
    • >> Go to DataMiner Docs
  • DevOps
    • About the DevOps Program
    • Sign up for the DevOps Program
    • DataMiner DevOps Support
    • Feature Suggestions
  • Downloads
  • Swag Shop
  • PARTNERS
    • Business Partners
    • Technology Partners
  • Contact
    • Sales, Training & Certification
    • DataMiner Support
    • Global Feedback Survey
  • >> Go to dataminer.services

How to upgrade Generic Ping elements from v2 to v3?

16 views4 hours agoGeneric Ping
0
Martin Vrzba [DevOps Advocate]645 4 hours ago 0 Comments

Hi,

We are still using elements Generic Ping v2.1.0.11 and need to upgrade them to v3.1.2.15 without recreating the elements as they are linked to services, etc. However, upon changing the protocol version in the same element, the first index’s description from v2 is used as parameter description in v3, best explained on below screenshots. This affects all rows in the v3 ping element as it is a parameter description that is different. Even the Description in Ping v2 first line is set to “None” (Not initialized) or empty string “”, the column parameter description is still “Ping 01 Status”.

The rows are not migrated, but that's not the issue, we have script that can export before/import after upgrade.

Can this be fixed with some special SetParameter() method or other SLNet message while still in v2 or after upgrade to v3?

To replicate, create a Generic Ping element v2, add one row with description, change version to v3, see column header and parameter description.

Thank you.

Ping v2

Ping v3

Martin Vrzba [DevOps Advocate] Edited question 4 hours ago

0 Answers

  • Active
  • Voted
  • Newest
  • Oldest
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

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin