Skip to main content
Solved

AWS SNS Issue

  • May 9, 2025
  • 2 replies
  • 38 views
deanhowell
Influencer
Forum|alt.badge.img+24

I have a 2023.2.1 workbench that reads in a JSON file using the TextLine reader, does some FME magic and the outputs the results for FME Server (Flow) to use.

2023.2.1 workbench to process JSON

The reader parameters are set to read the whole file at once

The workbench is published to FME Flow 2023.2.1 and is used in an Automation that gets an AWS SNS message with the JSON info in the message of the SNS.

 

The SNS is received as expected but the message appears to be reading each line as a separate source and as such it never processes the file as expected.

 

 

Any advice as to what I am doing wrong in the process?

Best answer by takashi

Hi ​@deanhowell ,

It seems that the Log says the dataset parameter of a Text File reader recieved incorect file path strings - e.g. "{", "Type : Notification,", etc. Those strings are not file path strings, so naturally the workspace fails.


If you are attempting to pass a JSON document created in the first workspace to the second one through the output from FME Flow Automations writer, you can receive the document directly through a Text type user parameter, instead of using a Text File reader.

FME - My go to no code development tool
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.

2 replies

takashi
Celebrity
  • takashiCelebrity
  • 7843 replies
  • Best Answer
  • May 9, 2025

Hi ​@deanhowell ,

It seems that the Log says the dataset parameter of a Text File reader recieved incorect file path strings - e.g. "{", "Type : Notification,", etc. Those strings are not file path strings, so naturally the workspace fails.


If you are attempting to pass a JSON document created in the first workspace to the second one through the output from FME Flow Automations writer, you can receive the document directly through a Text type user parameter, instead of using a Text File reader.

Why not inspect features with Visual/Data Preview and Feature/Record Information before writing them into a destination dataset?
deanhowell
Influencer
Forum|alt.badge.img+24
  • deanhowellInfluencer
  • Author
  • Influencer
  • 315 replies
  • May 9, 2025

Thanks ​@takashi, I removed the file reader and add the parameter as suggested. It took a few iterations to get the right combination but all looks good now :)

 

 

FME - My go to no code development tool

Community Stats

32,100
Posts
121,893
Replies
39,744
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.