I'm trying to use the WHERE Clause in a FeatureReader. I'm reading in an Oracle SDE featureclass and want to only select those records that match an attribute in a csv file I've loaded. I'm assuming that I have everything setup correctly where the attributes from the csv file are FME Feature Attributes. It seems when I add the @Value(col0) to my WHERE Clause, it breaks. How can I check to make sure it is setup correctly?
Question
Using the WHERE Clause in a FeatureReader to search for features based on input parameters from a csv file.
How does it break? Do you have a log file or log message that you can share that might help us identify where the problem is occurring. Sharing your workspace can also help the community identify where a problem lies.
markatsafe wrote:
How does it break? Do you have a log file or log message that you can share that might help us identify where the problem is occurring. Sharing your workspace can also help the community identify where a problem lies.
Could not find the features in the table 'SCHEMA.TABLE'. One possible reason is that a WHERE clause was specified that references a column/field that does not exist in the table. The error number from ArcObjects is: '-2147216072'. The error message from ArcObjects is: {Underlying DBMS error [ORA-01722: invalid number] [SCHEMA.TABLE]}
Attached is my configuration for the FeatureReader and WHERE Clause.
capture.jpg
+17- Contributor
From the Error message, I take it Col0 maps to a char field. Your where clause in that case should be WHERE <field> = '@Value(col0' . That is including the quotes!
erik_jan wrote:
From the Error message, I take it Col0 maps to a char field. Your where clause in that case should be WHERE <field> = '@Value(col0' . That is including the quotes!
+3- Contributor
I am having the same sort of issue in FME 2022 with the feature reader. For regular values such as Ashfield,, the following where clause works fine: NAME IN ('@Value(Rspctve_UG_Name)'). Ashfield being both the value in Rspctve_UG_Name and the value in NAME. But where there is a hyphen, such as PROJECT 406 - LEEDERVILLE, the statement finds no features and I receive the warning above that the where clause has returned no features. How can both scenarios be accommodated?
I should add that for hyphenated values the following does work: NAME IN (@Value(Rspctve_UG_Name)). But it then doesn’t work for non-hyphenated values.
Reply
Rich Text Editor, editor1
Editor toolbars
Press ALT 0 for help
Helpful Members This Week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.