Skip to main content
Question

FME 2018.1 JSONFragmenter Result Attribute parameter greyed out

  • June 1, 2018
  • 5 replies
  • 22 views

Forum|alt.badge.img

I am having a problem with a JSONFragmenter transformer. Though I think I set up all the parameters correctly I am getting the Result Attribute (for the resulting output) greyed out and I don't understand why (see below). Can anyone help?

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

nielsgerrits
VIP
Forum|alt.badge.img+60
  • 2940 replies
  • June 1, 2018

The result fragment will replace the source attribute when using Attribute as Source. The Result Attribute is only in use when reading json from file or URL. Also see documentation.

"If the JSONFragmenter is set to read JSON from a feature attribute, then the output is automatically written to the input attribute. If, however, the JSONFragmenter is set to read JSON from a file or URL, then an output attribute must be selected. This is done in the Result Attribute field which is activated when Input Source is set to File/URL. The output attribute may be selected from existing input attributes, user defined parameters, or a new attribute may also be created."

http://docs.safe.com/fme/2018.1/html/FME_Desktop_Documentation/FME_Transformers/Transformers/jsonfragmenter.htm


takashi
Celebrity
  • 7843 replies
  • June 1, 2018
FME 2018.1 is a beta version. It's still in developing stage, could have many issues.

 

I would recommend you to use the latest release version 2018.0.1, if the workspace is for a mission critical task.

Forum|alt.badge.img
  • 51 replies
  • September 14, 2018

The result fragment will replace the source attribute when using Attribute as Source. The Result Attribute is only in use when reading json from file or URL. Also see documentation.

"If the JSONFragmenter is set to read JSON from a feature attribute, then the output is automatically written to the input attribute. If, however, the JSONFragmenter is set to read JSON from a file or URL, then an output attribute must be selected. This is done in the Result Attribute field which is activated when Input Source is set to File/URL. The output attribute may be selected from existing input attributes, user defined parameters, or a new attribute may also be created."

http://docs.safe.com/fme/2018.1/html/FME_Desktop_Documentation/FME_Transformers/Transformers/jsonfragmenter.htm

 

I just had this happen to me, I upgraded my workbench to 2018.1 and this transformer stopped working. Finally i re-selected the json attribute and found that in the upgrade it had reset to read from file/url.

xiaomengatsafe
Safer
Forum|alt.badge.img+11
  • Safer
  • 324 replies
  • September 17, 2018

 

I just had this happen to me, I upgraded my workbench to 2018.1 and this transformer stopped working. Finally i re-selected the json attribute and found that in the upgrade it had reset to read from file/url.
Hi @brianapeters, Thanks for bringing this to our attention. We were able to reproduce the problem. It does seem like something went wrong in this transformer, when an 2018.0 workspace was opened in 2018.1. We will investigate and send you an update, when this issue is fixed. Thanks again!

 


xiaomengatsafe
Safer
Forum|alt.badge.img+11
  • Safer
  • 324 replies
  • October 1, 2018

 

I just had this happen to me, I upgraded my workbench to 2018.1 and this transformer stopped working. Finally i re-selected the json attribute and found that in the upgrade it had reset to read from file/url.
Hi @brianapeters, Just an update: we added some fix in the latest FME 2018.1. It should resolve the type of issue you encountered. Please find the latest release here. And if you have any more issues with the latest version, please let us know.