+1
I have the problem that we can create collection variables, but in none of the actions is the created collection variable available. I checked the version comparisons for Standard vs. Enterprise and could not find any indication that the collection functions are restricted in the Standard edition.
Can this be a missing or incorrect configuration at the installation, or a version bug?
Best regards
could you explain what exactly you'd like to do with collection?
there're not too many actions that work on whole collection.
collections are usually processed so that you set up a for each loop to iterate over the collection elements and within the loop process single collection elements.
+1
so you mean collection is a variable where query list result set should be stored to?
that should normally be allowed...
could you post variable and query list action configuration?
+1
This ist the configuration in my trial enterprise version (Nintex WF 2013)
But in the live (Nintex WF 2013) Standard installation in can only create the collection variables, but never use.
your configuration is correct - it allowed you to congure collection var as a target variable where list of returned IDs is to be stored, as well as source collection in for each action.
what other exact place/field you'd like to use collection variable in???
But in the live (Nintex WF 2013) Standard installation in can only create the collection variables, but never use.
that might be a feature of that specific action...
even within on-prem workflows list of variables might be restricted just to those of supported datatype - eg within for each action for 'target collection' only collection variables are listed, or for index variable only numeric variables are listed
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
