Variable Concatenation Issue

Variable Concatenation Issue

avatar

RDM macOS 2026.3.0.5, .NET 10.0.12
Hierarchy: Company folder > subfolder > SSH entry

Company Custom field 1: somekey.pem
Global variable SSH_KEY_DIR: path/to/ssh/key/dir

Works in the SSH private-key path:
$SSH_KEY_DIR$/somekey.pem

Fails with “private key does not exist”:
$SSH_KEY_DIR$/$COMPANY_CUSTOM_FIELD1$

Both $COMPANY_NAME$ and $COMPANY_CUSTOM_FIELD1$ resolve
correctly in the same connection’s tab title.
The private-key path is configured directly in that connection.

All Comments (2)

avatar

Hello,

We will run some tests on our side to see what is happening. Just to be certain about the issue:
The custom variable related to the path of your private key doesn't work.

However, the variables related to the company name and company custom field resolve correctly.
Is that correct?

We are going to start running tests based on that premise. If we are wrong or you find anything relevant, please don't hesitate to communicate with us.

Michel Lambert

avatar
Hello,

We will run some tests on our side to see what is happening. Just to be certain about the issue:
The custom variable related to the path of your private key doesn't work.

However, the variables related to the company name and company custom field resolve correctly.
Is that correct?

We are going to start running tests based on that premise. If we are wrong or you find anything relevant, please don't hesitate to communicate with us.


@Michel Lambert
To clarify:

$SSH_KEY_DIR$ - a global custom variable, defined in settings > custom variables. Its value is my ssh key directory. (e.g. /Users/myuser/.ssh)
$COMPANY_CUSTOM_FIELD1$ - the specific ssh key file name, defined in the first custom variable field of the company entry (e.g. mykey.pem).

end goal: defining $SSH_KEY_DIR$/$COMPANY_CUSTOM_FIELD1$ in ssh key path, in an ssh session entry beneath the company,
be successfully resolved to /Users/myuser/.ssh/mykey.pem.

Issue: when pressing Save, a message claiming "ssh key not found" pops up, prevents saving. $SSH_KEY_DIR$/mykey.pem does work.

In the ssh session entry, in user interface > tab page title, when writing $SSH_KEY_DIR$/$COMPANY_CUSTOM_FIELD1$,
I can see the variable resolution is successful, and in the ssh session tab name I indeed see /Users/myuser/.ssh/mykey.pem, so it seems like an issue only with the ssh key path field.

This issue only happens on Mac; on my windows RDM, ssh key path is resolved successfully.