I am doing UiPath level-3 Assignment 1. I have made all the workflows using Ui Studio and I am stuck in the process workflow. While I run the WFs, it says
Process WF: Given dictionary is not present.
I checked all the values and arguments and they seem correct too.
Also when I run the Process WF separately, it gets stuck for each loop and say
object reference not set to an instance of an object.
Could someone help resolving these issues? Thanks in advance.
You are passing null value/trying to get value from dictionary using the key which doesn't exist. Please also remember that before using dictionary you have to create it.
It will be easier to help if you can provide status window logs at least.
As you said - I checked all the values and arguments and they seem
correct too.
So just check for spaces in your config file from where you are reading data and putting them in Dictionary.
Second Possibility
which seems to me is just check your arguments via which you are passing your configuration dictionary to your workflow. are you passing it from main workflow to your child workflows.
just double check your arguments.
Regards..!!
Aksh
Related
This is a question about using PowerShell with Custom Commands (or scheduled tasks) in the Adaxes Active Directory management software by Softerra.
I am trying to accept a parameter from a user when using a custom command, then I need to take that value and modify it for use in a future action of the custom command.
A "for example" use-case would be creating a script that sets a user's out of office, where the custom command takes a target user reference in the out of office message. The first action in the custom command would find the email address of the provided user, then the second action would set the out-of-office with a message telling recipients for immediate assistance to email the provided user's email address. I realize there may be ways to solve this with one PowerShell script, but there are MANY scenarios where it would be beneficial to process provided information with a script action for use with MULTIPLE future actions in the custom command.
I already know how to access parameter values in custom commands for Softerra Adaxes, but I can't figure out how to WRITE to parameter values.
Accessing values:
$context.GetParameterValue('param-Example')
Does anyone know how to write TO parameter values? $context.SetParameterValue() does not work. This would be extremely useful for being able to store and manipulate values between actions in custom commands in Adaxes.
If anyone is looking for something similar, the answer I got from Adaxes support was that there is no means to do this currently with their software.
The only work-around would be writing to a property of the object being modified, then reference that property later.
For instance, writing a value to the extensionAttribute1 property of a user, then referencing that later in the script in a different action.
If anyone comes up with a better solution or Adaxes changes this, please feel free to suggest a better solution!
Has anyone found a way to delete an environment property from UDeploy via a REST call? I grabbed the call made via the UDeploy site when I delete a variable in Environment=>Configuration=>Environment Properties but I get a "Conflict" each time I attempt it.
Thanks for your thoughts,
Patrick``
Please take a look at: https://www.ibm.com/docs/en/urbancode-deploy/7.0.5?topic=commands-removeenvironmentproperty
If there's an old name of property (i.e. without p: prefix) in the call, rest call might return 'Conflict'. Please see Warning: https://www.ibm.com/docs/en/urbancode-deploy/7.1.1?topic=properties-referring
Is it possible to get the values for custom variables being used in the build? I know they can be dumped to the console output as per what this example describe. But still want to find an easier way to archive it.
http://www.codewrecks.com/blog/index.php/2017/08/04/dump-all-environment-variables-during-a-tfs-vsts-build/
There isn’t the easier way then the way you provided to retrieve build variables, the value of variable can be changed during the build time (Logging Command), so it’s better to retrieve the variable at the end of the build (the way you provided).
Note, the secret variables can’t be output as general text.
I'm playing with DIXF and following Alex's blog http://ax2012aifintegration.blogspot.com/2014/05/microsoft-dynamics-ax-2012-file_4600.html?showComment=1405542006070#c2497509467713291887
I'm stuck on creating a batch job that has two tasks -- one for getting data from staging table and another for exporting teh data from staging table to a flat file.
The first task requires that I invoke DMFStagingWriter class. The AX-shipped version doesn't have the canGoBatchJournal set to true; so the class doesn't show in the task list. I overrode that method and returned a value of true. I compiled the class and generated an incremental CIL. However, when I try to use that class in the batch task list, it doesn't show. If I type it in, AX says it is an invalid class.
What am I missing?
Thank you.
I found my own solution. It was a matter of simply getting out of Ax and coming back in to resolve the issue.
Given this command:
MSBuild.exe build.xml /p:Configuration=Live /p:UseMerge=true /p:EnableUpdateable=false
how can I form a string like this in my build script:
UseMerge=true;EnableUpdateable=true
where I might not know which properties were used at the command line.
What are you going to do with the list?
There's no built in "properties that came via the commandline" thing a la splatting in PowerShell 2.0
Remember properties can come from environment variables and/or other scripts.
Also, you stripped on of the params out in your example.
In general, if one is trying to chain to another command, one uses defaulting (Conditions on elements in PropertyGroups) and validation (Messages Conditional on presence of options) and then either create a new property or embed the params you want to pass into a string.
Here's hoping someone has a nice neat example of a more general way to do this but I doubt it.
As covered in http://www.simple-talk.com/dotnet/.net-tools/extending-msbuild/ one can dump out the parameters passed by doing /v:diag on the commandline (but that's obviously not what you're after).
Have a look in the Common.targets files - you'll find lots of cases of chaininign involving manaully building up lists to pass onto subservient tasks.