NOTE: Dollar notation is used to access object properties in .
If you want to user dollar notation in scripts with it representing access to column names, the character must be doubled to mask.
In Windows PowerShell scripts, instead of:
theScript.AppendLine("foreach ($Domain in $Domains)")
theScript.AppendLine("foreach ($$Domain in $$Domains)")
If you are using dollar ($) notation you need to ensure that the value is allocated the correct data type. Dollar notation returns a "String" type as default. If another data type is given it is internally converted with "ToString".
Permitted data types are:
$<column name>:<data type>$
The Active Directory user display name should comprise of the first and last name of the Active Directory user. The template for ADSAccount.Displayname is:
If $Givenname$<>"" And $Surname$<>"" Then
Value = $Surname$ & " " & $Givenname$
ElseIf $Givenname$<>"" Then
Value = $Givenname$
ElseIf $Surname$<>"" then
Value = $Surname$
If an employee is disabled, the leaving date should be set. The template for Person.Exitdate is:
If $IsInActive:bool$ Then
Value = Date.Today
The only relation currently permitted is the foreign key relation.
$FK(<foreign key column>).<column name>:<data type>$
An Active Directory user’s first name should based on the assigned employee. The template for ADSAccount.Givenname is:
Value = $FK(UID_Person).Firstname$
Optional process step parameters are not generated if the value is set to "Nothing" or the value template is not assigned. This makes it possible to limit the number of parameters for target system components. If such a value should be emptied then an empty string should be given instead of "nothing".
A value template may look like this:
If $Lastname[o]$ <> $Lastname$ Then
Value = $Lastname$