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

Disabled DVE not being removed from surveyor

Solved650 views13th May 2024DVE NotifyDataMiner SET_ROW
2
Kristopher Brookshire [DevOps Member]220 6th May 2024 2 Comments

Hello Guys,

I have a connector that is enabling and disabling DVE’s in another connector using protocol.NotifyDataMiner(225 /*NT_SET_ROW*/, rowDetails, rowData);

The enable is working as expected, the DVE is enabled on the remote connector and appears the DVE appears in the surveyor. I am running into an issue with the disable. It sends the SET_ROW to disable and it changes in the remote connector but the DVE is not removed from the surveyor.

Do you know any reason that this would not be working?

Kristopher Brookshire [DevOps Member] Selected answer as best 13th May 2024
Rene De Posada [SLC] [DevOps Advocate] commented 6th May 2024

Hi Kristopher, toggling the status to “disabled” in the row should resolve in two things:
1. The status goes to “Disabled” in the visual. This is working for you.
2. The action of removing the DVE element is actually executed. This is not working for you.

Without knowing the details of the connector integration, could it be that the interelement set is only triggering the visual part and that another necessary step (e.g., check if the element exists) is not captured by the set?

Did it ever work? Are you able to do it manually directly in the DVE parent element?

Thanks,

Kristopher Brookshire [DevOps Member] commented 6th May 2024

Hello Rene,

That is correct. This is a new connector and this has not worked so far. Yes if I reenable then disable from the parent it works.

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
1
João Severino [SLC] [DevOps Catalyst]13.01K Posted 7th May 2024 1 Comment

Hi Kristopher,

Given your answer to Rene’s question that when doing it manually it is working, it makes me conclude that the logic for enabling and disabling the DVE is on a trigger associated with the write parameter of your table.

When doing a set row, you are bypassing that logic and going directly to the “read side” of the control parameter.

My suggestions would be to either move the logic to execute on change of the read parameter or, and this would be my preferred approach, change the way you perform the set to point towards the write parameter associated with the enable/disable column.

To keep in line with the methods you are already using you could try the following notify call NT_SET_PARAMETER (50) | DataMiner Docs and in the part where it has this

uint parameterID = 10;

you would replace with the parameter id of your write parameter.

Kristopher Brookshire [DevOps Member] Posted new comment 13th May 2024
Kristopher Brookshire [DevOps Member] commented 13th May 2024

Thank you for your answer, this did fix my issue.

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