I am trying to have a list of strings to pass as parameter to my script:
when I start the script it displays:
With "Add Value' button disabled. What am I missing here?
-
There is 'solution' by adding Filter-Value List, but it is ugly– FelixIPCommented Mar 18, 2015 at 0:11
-
I was thinking that you wanted to enter multiple free format strings rather than choosing them from a list. Tool validation may be of assistance but will still not be pretty.– PolyGeo ♦Commented Mar 18, 2015 at 0:20
-
Yes I do want free format strings, using Value List was just an interim solution and I don't like it. This is about fixing missing paths in old mxds anyway– FelixIPCommented Mar 18, 2015 at 0:29
-
I've not done this but perhaps it can work. Use a second parameter to enter a single value string parameter and use tool validation to use that being entered to trigger update of your separate multi value string parameter.– PolyGeo ♦Commented Mar 18, 2015 at 0:32
-
There appears to be another approach that incorporates ModelBuilder at gis.stackexchange.com/questions/17821/… It seems a little unintuitive but sounds like it may work and be simpler than tool validation.– PolyGeo ♦Commented Mar 18, 2015 at 0:37
|
Show 1 more comment
1 Answer
Use the "Any Value" data type instead of the "String" data type. I have no idea why multivalue strings don't work, but it's very counterintuitive...
-
I am accepting this although it was one of the solutions I've checked. I was looking for true string inputs because they are not enclosed in ' symbols, even if there are \ symbols inside the string. This is convenient when working with folders (non-existing things from old mxds)– FelixIPCommented Mar 18, 2015 at 1:31