nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Pro 3.0.2: The “select by attributes” tool has “the expression can’t be edited in clause mode” issue when working with SQL option,

JamalNUMAN

As per the screenshot below, I couldn’t figure out why the “select by attributes” tool has “the expression can’t be edited in clause mode” issue when working with SQL option,

What might be the problem here?

Find more posts tagged with

Accepted answers

All comments

BarryNorthey

Try wrapping %school% in single quotes '%school%' not double quotes "%school%".

JamalNUMAN

With same syntax, the obtained error message now makes sense as per the screenshot below. Why was the Pro giving the “the expression can’t be edited in clause mode” error that doesn't make any sense?

BarryNorthey

When I built a selection query in clause mode it wrapped the target info I was looking for in single quotations, not double quotes and it turns red when displayed in SQL mode. In my example I am selecting anyone with initials J (text) in field INITIALS:

When I replace single quotes with double quotes in SQL mode and then try to return to clause mode I get the message you are getting and the entry in double quotes appears as black text.

I assume the warning “the expression can’t be edited in clause mode” is letting you know that you can't switch from SQL mode to clause mode as it doesn't recognize the syntax used (double quotes).

JamalNUMAN

What’s meant by “clause mode”? how the script is recognized as “clause mode”?

BarryNorthey

Selection queries can be built in Clause mode or directly in SQL mode as explained here: https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/basics/query-builder.htm

Queries built in Clause mode (interactive helper primarily for those that don't know how to structure a SQL query). It can be viewed in SQL mode by toggling mode to on. This is the actual SQL expression that Pro uses. You can also toggle SQL off and return to Clause mode.

You can also go directly to SQL mode directly and build your query but it is possible that the syntax you used is not recognized by Clause mode or there is an error that prevents opening clause mode, such as double quotes vs single quotes. (don't know).

PaulMason

I am also looking for an answer to this problem. It is a mode issue (as mentioned in the error message). So I just want to know how to restore the usual "Where..." mode so that I can select the Field, Operator, and enter a value. It would also be nice to know why this "clause" mode became active without me explicitly setting it?

PaulMason

...excuse me, it IS in clause mode but it beats me why the SQL button is jammed and cannot be toggled. I guess the "Where" (with arguments) will appear when SQL is Off.

ElenaFavaro

I found this bug report that might be helpful: https://support.esri.com/en-us/bug/the-warning-the-expression-cant-be-edited-in-clause-mod-bug-000113319

I was also stuck in "clause mode". I deleted the predefiend expression in the comment box, and then was able to toggle SQL off.

petersck

This worked for me - thanks Elena!

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.