Skip to main content
Solved

JSONFragmenter raises error if specified file path contains spaces


takashi
Influencer

Hello,

FME 2019.0.1 build 19253

I noticed the JSONFragmenter raises an error if the specified file path contains spaces.

0684Q00000ArDH0QAN.png

JSONFragmenter (JSONQueryFactory): The clause 'FILEPATH_OR_URL folder name/test-geojson-structure.json' within 'FACTORY_DEF * JSONQueryFactory FACTORY_NAME JSONFragmenter INPUT FEATURE_TYPE Creator_CREATED MODE EXPLODE EXPLODE_FORMAT JSON REJECT_EMPTY_LISTS YES EXTRACT_ATTR No JSON_ATTR <Unused> READ_FROM_FILE YES FILEPATH_OR_URL folder name/test-geojson-structure.json OUTPUT_ATTRIBUTE _result EXPLODE_QUERY json<openbracket><quote>features<quote><closebracket><openbracket>*<closebracket> RECURSIVE_FLATTEN <Unused> OUTPUT EXPLODED FEATURE_TYPE JSONFragmenter_FRAGMENTS OUTPUT REJECTED FEATURE_TYPE JSONFragmenter_<REJECTED>' is incorrect.  The parameter to FILEPATH_OR_URL must be a constant value, a value-of (&) attribute, or an FME function call

The clause 'FILEPATH_OR_URL folder name/test-geojson-structure.json' within 'FACTORY_DEF * JSONQueryFactory FACTORY_NAME JSONFragmenter INPUT FEATURE_TYPE Creator_CREATED MODE EXPLODE EXPLODE_FORMAT JSON REJECT_EMPTY_LISTS YES EXTRACT_ATTR No JSON_ATTR <Unused> READ_FROM_FILE YES FILEPATH_OR_URL folder name/test-geojson-structure.json OUTPUT_ATTRIBUTE _result EXPLODE_QUERY json<openbracket><quote>features<quote><closebracket><openbracket>*<closebracket> RECURSIVE_FLATTEN <Unused> OUTPUT EXPLODED FEATURE_TYPE JSONFragmenter_FRAGMENTS OUTPUT REJECTED FEATURE_TYPE JSONFragmenter_<REJECTED>' is incorrect.  The parameter to FILEPATH_OR_URL must be a constant value, a value-of (&) attribute, or an FME function call

See also the attachment: 

Best answer by mark2atsafe

These transformers now allow use of a filename with a space in them. It will be in any build 19621 or greater (so 2019.2 or even 2019.1 if a newer version such as 2019.1.2 is posted). No word on using an attribute for the parameter though.

View original
Did this help you find an answer to your question?

5 replies

mark2atsafe
Safer
Forum|alt.badge.img+44

Thanks for letting us know, Takashi. I've filed this as an issue with the developers and I hope that they will fix it soon.

The reference number for the issue is FMEENGINE-60151

Regards

Mark


mark2atsafe
Safer
Forum|alt.badge.img+44
mark2atsafe wrote:

Thanks for letting us know, Takashi. I've filed this as an issue with the developers and I hope that they will fix it soon.

The reference number for the issue is FMEENGINE-60151

Regards

Mark

I notice that it also affects the JSONExtractor and JSONFlattener, so I've mentioned that to the developers as well.


takashi
Influencer
  • Author
  • May 22, 2019
mark2atsafe wrote:

Thanks for letting us know, Takashi. I've filed this as an issue with the developers and I hope that they will fix it soon.

The reference number for the issue is FMEENGINE-60151

Regards

Mark

Hi @mark2atsafe, thanks for filing the problem report.

Additionally, I think it would be a good enhancement if an input feature attribute could be set to the File/URL parameter optionally.


mark2atsafe
Safer
Forum|alt.badge.img+44
  • Safer
  • Best Answer
  • September 3, 2019

These transformers now allow use of a filename with a space in them. It will be in any build 19621 or greater (so 2019.2 or even 2019.1 if a newer version such as 2019.1.2 is posted). No word on using an attribute for the parameter though.


takashi
Influencer
  • Author
  • September 4, 2019
mark2atsafe wrote:

These transformers now allow use of a filename with a space in them. It will be in any build 19621 or greater (so 2019.2 or even 2019.1 if a newer version such as 2019.1.2 is posted). No word on using an attribute for the parameter though.

Good to hear. Thanks for the fix and you notification.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings