Skip to main content
  • EN

I have created a workspace which takes multiple zipfiles as a user parameter and reads them with a FeatureReader containing an Directory and File Pathnames Format. If I run this workspace in FME Desktop 2021.2 it works fine.

My next step is publishing it to FME Server 2021.2 and starting it there.

I add the same files to the user parameter and request the workspace to run.

It starts like it should and gets the filenames as parameters but then it gets weird. FME Server seems not able to process the parameter it created itself.

On the FeatureReader it gives an error which tells me the FeatureReader (QueryFactory): The clause '@EvaluateExpression(... is in correct.

I asked several colleagues and searched the internet on this specific error but  I can't find anything that looks like this.

 

So did anyone ever run into this error and does one know how to fix it?

 

The complete error (without the file paths which are formatted like "D:/ProgramData/Safe Software/FME Server///resources/system/temp/upload//Testing/Velddata - KLIC2TerraIndex - v1.0.fmw/administrative_agent/Levering_23G0635414_1.zip") is:

 

2023-11-3 12:12:37 | FeatureReader (QueryFactory): The clause '@EvaluateExpression(FDIV,STRING_ENCODED,D:/....zip D:/....zip D:/....zip D:/....zip,FeatureReader)' within 'FACTORY_DEF {*} QueryFactory FACTORY_NAME { FeatureReader } INPUT FEATURE_TYPE Creator_4_CREATED FCTQUERY_INTERACTION NONE COMBINE_ATTRIBUTES { RESULT_ONLY } IGNORE_NULLS { <Unused> } QUERYFCT_ATTRIBUTE_PREFIX { <Unused> } COMBINE_GEOMETRY { RESULT_ONLY } ENABLE_CACHE { NO } QUERYFCT_TABLE_SEPARATOR { SPACE } READER_TYPE { PATH } READER_DATASET { @EvaluateExpression(FDIV,STRING_ENCODED,D:/....zip D:/....zip D:/....zip D:/....zip,FeatureReader) } QUERYFCT_IDS { } READER_DIRECTIVES { METAFILE,PATH } QUERYFCT_OUTPUT { BASED_ON_CONNECTIONS } CONTINUE_ON_READER_ERROR YES QUERYFCT_RESULT_TAGS { PATH } QUERYFCT_SET_FME_FEATURE_TYPE YES READER_PARAMS_WWJD { RECURSE_DIRECTORIES,NO,NO_EMPTY_PROPERTIES,YES,EXPOSE_ATTRS_GROUP,FME_DISCLOSURE_OPEN,TYPE,ANY,RETRIEVE_FILE_PROPERTIES,NO,OFFSET_DATETIME,yes,USE_NON_STRING_ATTR,yes,PATH_EXPOSE_FORMAT_ATTRS,fme_dataset<comma>char<openparen>50<closeparen><space>fme_basename<comma>char<openparen>50<closeparen>,GLOB_PATTERN,* } TREAT_READER_PARAM_AMPERSANDS_AS_LITERALS YES OUTPUT { READER_ERROR FEATURE_TYPE FeatureReader_<REJECTED> } OUTPUT PATH FEATURE_TYPE FeatureReader_PATH' is incorrect. The parameter to READER_DATASET must be a constant value, a value-of (&) attribute, or an FME function call

 

 

Hi @rienco​,

I've had a few issues with file paths and FME Server or even workspace runners.

Most of the time the issue has been with how the paths have been created.

 

Are you able to post a screengrab of your feature reader parameters?

Also, have you tested creating the path as an attribute?

Since I did not have time to look into it any further a college of mine took over. He fixed the problem by processing the multi file input parameter in another way.

We now first fetch the user parameter as an attribute. It then contains the list of filenames but in one string with spaces as delimiters.

Because the space is not a useful delimiter, we now split it using '.zip'. A workaround but it works both in FME Desktop as in FME Server.

 

image

Reply


Community Stats

30,162
Posts
114,480
Replies
37,807
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.