I have been successful in creating my first ever DVE protocol after a bit of a steep learning curve, it's using the Weather Underground API to poll a table of Personal Weather Stations (PWS) and then for each PWS to automatically get created into it's own DVE.
However the child elements still append the display key from the parent DVE table which is undesirable behaviour
I tried Information Templates and an ExportRule Regex on the Parameter Description just to get rid of the integer to start with, but as the parameter name within the element data display is already just "Temperature" I didn't think that was going to help me 🙁
Same scenario as this previous question from over 4 years ago. Is there a way that this can now be achieved to just have a straight parameter description in the alarms console?
Hi Sam,
Great to hear you got your first DVE protocol working with the PWS data. That’s a solid achievement!
Regarding your question about simplifying the DVE alarm description so that it only shows the parameter description (e.g., just “Temperature” in the alarms console):
-
Current behavior is by design
In DVE setups, the alarm description is inherently linked to the primary key or display key of the parent DVE table row. That key is used when generating:- The DVE element name, and
- The alarm descriptions for table-based parameters.
This is done to ensure:
- Each alarm can be uniquely tied back to a specific row/child DVE, and
- The system can reliably map alarms to the correct PWS instance.
-
Why the display key/integer cannot be removed
Because DVE parameters are table parameters, they must remain associated with their parent table row via the display/primary key. According to the current DataMiner behavior and documentation, this reference is required to:- Avoid ambiguity when there are many similar parameters across different DVEs, and
- Prevent incorrect mappings or duplication of parameters across child elements.
As a result, the display key (or integer) is always included as part of the alarm description and cannot be stripped out so that only the “plain” parameter description remains.
-
No supported workaround at this time
- Information Templates and ExportRule Regex do not influence the format of DVE alarm descriptions in this way.
- There is currently no supported configuration or recent feature that allows you to remove the display key/integer from the alarm description and show only the parameter description in the alarm console.
Summary
At this time, DataMiner does not support customizing DVE alarm descriptions to exclude the display key or integer. The current behavior is required to ensure correct operation of DVEs and to maintain a reliable mapping between alarms and their corresponding table rows/child elements.
Refs: Dynamic Virtual Elements | DataMiner Docs, Implementing DVE functionality | DataMiner Docs
Kind Regards,
Luís Freitas