Learning

Hi Dario, you can consider using an after trigger and use conditions to decide if another Get is required

Hi Sergio, There isn’t any faster way (at least that I can think of) to remove keys other than repopulating the table or clearing all keys like Edib or Michiel …

Hello everyone, Thank you for your support. Since the toggle buttons consist of two overlapping shapes, the primary issue was that the existing design used a “NoConfirmation” option, which needed …

Hi Maximiliano, This is a known issue which has been resolved in DataMiner 10.4.0 (CU1) and 10.4.4 (see docs). Is it possible that you’re on a lower version?

Hi Stefan, You can use the Element.GetTablePrimaryKeys to get the table keys. Then you can use a foreach loop to go over all your table keys. Element myElement = engine.FindElement(“My …

Based on the investigations, we used the low-level .Net communication to get the desired information and create a custom JSON parser to parse and get the data needed.

Right, nothing to do with the context menu: engine.GetDummy(“vmatrix”).Name -> engine.GetDummy(“vmatrix”).ElementName and it works 😉

Can it be an optional on the section but none optional on an state? we have had a few of these mismatches in the past

Hi Gerwin, When the context menu contains the option options=”table:selection”, it will pass along all the selected primary keys to the logic behind it. You should be able to do …

Regarding your first question: currently DataMiner will only read out the Email, Givenname, Surname & Groups Claims, other data, like your pager claim, will be ignored. Unfortunately, I don’t believe …