Hi Daniel,

Fortunately, you don’t need an automation script or anything similar to achieve what you want. There are several ways to get the same result, and the best approach depends on your exact use case.

1. When the column you need to compare in Element B is not a display key or primary key

In that case, you will need to use a subscription filter.

You can use the SubscriptionFilter shape data, which is commonly used when filtering data. The filter references the first column in Element B and compares it with a value from Element A (via a param placeholder) (e.g. value=304 == [param:172/87,21]). After applying the correct filter, you can use the same placeholder in the shape text to display the second column from Element B (e.g. [param:172/240,302,]).

Alternatively, you can use ParameterSubscriptionFilter, which is a more specific variant. This allows you to use the Parameter shape data directly, so you don’t need to use param placeholders in the shape text. A benefit of this method is that you can use Options (e.g. HideUnit) as well as the |Alarm suffix to show the alarm color of the parameter.

Important note:
When your filter matches multiple rows, the behavior differs between the two filter types:

• SubscriptionFilter returns all matching values, joined with a pipe.
  For example: West|South
• ParameterSubscriptionFilter only returns the first matching result.
  For example: West

You can find more info on the syntax here: Dynamic table filter syntax | DataMiner Docs.

2. When the comparison column in Element B is a display key or primary key

In that case, things are easier: you can directly reference the parameter of Element A in the Parameter shape data to point to the right row.
Example:
302,[param:172/87,21]

Hope this helps you further!

Jarno