Skip to main content
Solved

JSONFragmenter raises error if specified file path contains spaces

  • May 22, 2019
  • 5 replies
  • 26 views
takashi
Celebrity

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.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

5 replies

mark2atsafe
Safer
Forum|alt.badge.img+56
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • May 22, 2019

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

FME Evangelist to the Rich and Famous!!
mark2atsafe
Safer
Forum|alt.badge.img+56
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • May 22, 2019

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.

FME Evangelist to the Rich and Famous!!
takashi
Celebrity
  • takashiCelebrity
  • Author
  • 7843 replies
  • May 22, 2019

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.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
mark2atsafe
Safer
Forum|alt.badge.img+56
  • mark2atsafeSafer
  • Safer
  • 2554 replies
  • 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.

FME Evangelist to the Rich and Famous!!
takashi
Celebrity
  • takashiCelebrity
  • Author
  • 7843 replies
  • September 4, 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.

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

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?

Community Stats

32,079
Posts
121,818
Replies
39,714
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.