Hi Dojo,
I have several tables that link to one another using relations and foreign keys. These tables belong in a treeview and I want to have alarm bubble up using those relations. In one of my tables, I have multiple foreign keys that lets it control where in the treeview a specific row will appear. I have an issue now where the first relation that fits is always used so alarms only bubble up according to that relation, but my other rows in that table that don't follow the first relation (e.g. it should appear in a different part of my treeview and bubble up from elsewhere) don't bubble up correctly now. Is there a way for me to control which relations are taken at a row level?
Hi Joshua,
To be honest, it’s difficult to help you without the protocol itself, as this could be an issue with the protocol implementation or the software.
My advice is to first look into the element log to see if there are any missing table relations. If so, fix them by adding the missing relations.
An example of the error I’m referring to is shown below.
If the issue persists, please create a ticket using the Support application.
Support application | DataMiner Docs
Please include all the details you can (including the protocol or even a DELT of the element) so that the investigation can go smoothly. More info:
Collecting data to report an issue to Technical Support | DataMiner Docs
Kind regards,
Luís Freitas
UPDATE:
In my investigation, I found that there was a new feature request(https://collaboration.dataminer.services/task/156736) to allow DataMiner to choose which table relation to follow when there are multiple relations allowed. At this stage the feature seems to still be on the backlog.