Populate a parameter in report dynamically

Question

I have report which is listing all the users. I have a parameter for departments which is used as filters and it is a checkbox list. I am using this in report so we can filter the users based on the selceted departments and it is working well.

The report is using script to use the parameter and filter the users as per selected departments. This parameter is now manually populated with values of all departments we have so far. Is there a way in script I can dynamically get a list of departments and populate this parameter.

Answer 1

Hello,

Yes, it is possible. Unfortunately, we do not have the exact script, but the following one should be helpful: https://www.adaxes.com/script-repository/update-custom-command-parameter-values-based-on-unique-property-values-s527.htm.

Comments

Hello,

The script we referenced is just an example. You cannot directly use it for reports and it is expected to fail. Here is another example that might be helpful: https://www.adaxes.com/script-repository/add-value-to-drop-down-list-parameter-s632.htm. Pay attention that this script is intended for external execution. In your case (using a custom command), a lot of code will be gone from the script.

---

Just to provide clarity which I missed in my previous message, I am using the script in a custom command. Running it from the custom command itself.

Custom command setup

Custom command with script:

Script used in Custom command for testing:

$commandDN = "CN=Active Users report,CN=Users,CN=BC Custom Reports,CN=Reports,CN=Reports Root,CN=Configuration Objects,CN=Adaxes Configuration,CN=Adaxes" # TODO: modify me
$parameterName = "param-departmentauto" # TOOD: modify me
$propertyName = "department" # TOOD: modify me

# Bind to the custom command
$command = $Context.BindToObjectByDN($commandDN)
$Context.LogMessage($command, "Information")
# Get parameter
$parameters = $command.Parameters
$parameter = $parameters | Where {$_.Name -eq $parameterName}
if ($NULL -eq $parameter)
{
    $Context.LogMessage("Parameter '$parameterName' not found in Custom Command '$commandName'.", "Warning")
    return
}

return 

---

Hello,

As it was mentioned in the previous post, your script will always fail and that is expected. You are trying to use the approach which only works for custom commands with a report. Have a look at another example we referenced. It should be helpful.

---

I see okay got it, thank you. I notice the other script uses ADSI. Can this script be created as custom command and then use a business rule to schedule or trigger this.

Overall here is our goal We want to maintain a list of unique departments within Adaxes. Currently we are achieving this through property patterns, where we have a list of department values which we enforce on user object creation form.

Now the idea is to make this automated where we update that property pattern and then our report parameter where we are using department parameter gets updated automatically.

This is the first step in achieveing this goal where I will first learn to auto populate the report parameter in a automatd fashion, if this goes well then the second step is to provide a mehtod in Adaxes UI for our helpdesk team to update the property pattern which is our primary source for all list of departments.

I am still learning ADSI combination with powershell so I will try to use the example script you have provided, will comment back with more questions. As always appreciate Adaxes supports quick responses.

---

Hello,

Can this script be created as custom command and then use a business rule to schedule or trigger this.

Yes, it is possible, that exactly what we mentioned when referenced the script.