Skip to main content
Solved

AWS SNS Issue

deanhowell
Influencer
Forum|alt.badge.img+23

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.

View original
FME - My go to no code development tool
danilo_fme
1 person upvoted this
  • danilo_fme
    danilo_fme
Did this help you find an answer to your question?
This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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
Influencer
  • takashiInfluencer
  • 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.

deanhowell
1 person upvoted this
  • deanhowell
    deanhowell
deanhowell
Influencer
Forum|alt.badge.img+23
  • deanhowellInfluencer
  • Author
  • Influencer
  • 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

Helpful Members This Week

Community Stats

31,341
Posts
118,860
Replies
38,931
Members

Latest FME

Terms & ConditionsCookie settings

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
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.