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

DVE behavior in multiple views

Solved1.18K views16th February 2021DVE
2
Karel Lodefier [SLC] [DevOps Member]724 16th February 2021 0 Comments

Hi Dojo,

I notice different behavior when

  1. APPROACH 1
    1. STEP 1 – Create DVE parent element in multiple views
    2. STEP 2 – Create DVE child elements
    3. Result = both DVE parent and child elements are available in both views
  2. APPROACH 2
    1. STEP 1 – Create DVE parent element in 1 view
    2. STEP 2 – Create DVE child elements
    3. STEP 3 – Add DVE parent element in 2nd view
    4. Result = DVE parent element is available in both views, but the DVE child elements are only available in the first view

Why do we have different behavior? Is this expected?

Thinking at following use case: you have a chassis element with x card elements active and you want to add the chassis (with linked card elements) in a 2nd or 3rd view. Can we do this via standard operations in Cube?

Karel Lodefier [SLC] [DevOps Member] Selected answer as best 16th February 2021

1 Answer

  • Active
  • Voted
  • Newest
  • Oldest
1
Ive Herreman [SLC] [DevOps Enabler]13.57K Posted 16th February 2021 3 Comments

Hi Karel,

I believe this is expected behavior.

The DataMiner system will place the DVE children in the same view as the parent when they are created.
This way it’s easy to know where to find these children when they are created.

You have the flexibility to move the children and/or the parent to any other view, based on your preference.
If this would also move the associated parent and or children, you would lose flexibility, as this might not always be desired.

Please note that you can easily move multiple (dve) elements from one view to another view, by dragging a selection of elements from the element overview onto the surveyor if drag and drop editing is enabled in the surveyor.

Karel Lodefier [SLC] [DevOps Member] Selected answer as best 16th February 2021
Karel Lodefier [SLC] [DevOps Member] commented 16th February 2021

Hi Ive, thanks for your feedback on this!
Indeed, in Cube you can easily move a DVE parent and/or child element in the Surveyor. But in our use case, we want to add the DVE parent and child elements in a 2nd view. And here we have the struggle with DVE child elements (in Cube the Edit > Views is disabled).

Ive Herreman [SLC] [DevOps Enabler] commented 16th February 2021

Hi Karel,

When using the drag and drop functionality in cube, the elements will be moved by default. However, if you hold the ctrl-key while dragging the elements, you will make the elements available in a second view.

I typically remember this using a little trick:
the Ctrl key starts with the letter C, just like the word Copy.

Karel Lodefier [SLC] [DevOps Member] commented 16th February 2021

Perfect. Works fine. Many thanks Ive!

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