I am trying to concatenate a couple XY values
I have the X and Y fields (Double data type)
I created a Test field (string)
CONCAT(X, Y)
Then simply tried to calculate a simple test field
NAME - this is a field name
I get this error:
ERROR002536 Table Jurisdictions does not support or is in a state to support SQL Expressions
Any thoughts? Can do this in ArcMap in 2 seconds...ArcPro....ugggggg
python parser
X and Y , two fields
x = 10
y = 20
"{} {}".format(x, y)
'10 20'you would therefore use !YourField! for each of the x and y values.
String concatenation in python, or check out arcade. but vb stuff is the new cobol
That's guys....both do the trick....have to pick one for the answer....I like Dan's simpler approach but both answers are greatly appreciated....Still confused why simply SQL statements are not working in the SQL Expression Type
Somethin such as the below is failing
FieldName =
'TestingValue'
FieldName=
"TestingValue"
You said that you get
ERROR002536 Table Jurisdictions does not support or is in a state to support SQL Expressions
That's the error in Pro? Can you send a screenshot? What database are you working with (file, Oracle, SQL server, etc.?) and version?
This is ArcGIS Pro 2.1.2
I am simply hitting a shapefile - I havent tried on a GDB or SDE FC
my example was the most simplistic I could think of...why does it fail with SQL Expression, which is the main question in this thread...
I was able to get it working in Python3
shapefiles (yours) and geodatabase tables (mine) apparently don't support unless you 'do' something.
Maybe yours and mine is obviously not an sql thing. I never use sql, I had erroneously assumed that yours was a valid sql thing.
Which... according to the help are
Or like the help says in your previous post, an enterprise geodatabase table. So... a feature service or egdb table, not file gdb or shapefile.
I know that from the help... just waiting for Jay to see it
It says that SQL Expressions were implemented to better support bla bla bla.....I read it...Better support NOT will work with these file types and not these....would be nice if the text and documentation was a bit more specific.
A simple line - Will not work with gdb or shapefiles. 7 words eliminates all this confusion.
mystery solved... Kory will pass the comments on to Pro team I am sure.
you may as well close since Python expressions are much cooler anyway
I already have passed this feedback about the SQL expression section of the Calculate Field help to the geoprocessing team. Thanks!
Kory... this would also be a good place in the interface to put the 'verify' check box above the box rather than below and/or put all 'fail' cases in the 'messages' section when the expression fails.
Don't know if that is a big issue in updating tool verification and/or fail errors in tools. I find sometimes they aren't complete or you have to check in different places (if offered)
Don't have an answer for you; how do you use CONCAT(X,Y) in ArcMap? I get the same error as you in ArcGIS Pro using the SQL parser choice, but if fails in ArcMap for me. I've never used CONCAT(X,Y) before and had to google it just to find out what it is.
I got this simple Python def() to work in Pro: