Skip to main content
Question

Problem with wildcards for Filename (multiple) type parameter on FME Server (REST)


helmoet
Forum|alt.badge.img+8

Hi, I created an FME Workspace to process one or more files using an FFS reader. If I run it on FME Workbench is accepts a wildcard for the SourceDataset_FFS parameter. Even if I call it from a WorkspaceRunner it runs fine. However, If I post it to FME Server, I get the following response (HTTP/1.1 422 Unprocessable Entity): `_response_body' has value `valueD:\\Data\\FME\\FME%20Server\\Data\\LDR\\1_Secties\\*.ffsUnexpected value "D:\\Data\\FME\\FME%20Server\\Data\\LDR\\1_Secties\\*.ffs" for parameter "value," expected list'

Request url:

 

`myURL' has value `http://myfmeserver:8080/fmerest/v2/transformations/commands/submit/LDR/Stap_4_BerekenSectiesMetStationing.fmw?token=11111113289cef40e8bc340c3a63b3ff43405b00&detail;=low'

Upload body:

 

`UploadBody' has value `{ "FMEDirectives" : {}, "NMDirectives" : { "failureTopics" : [ ], "successTopics" : [ ] }, "TMDirectives" : { "rtc" : false, "description" : "LDR autorun LDR_Trigger_Handle_Notification", "priority" : 5, "tag" : "linux" }, "publishedParameters" : [ { "name" : "SourceDataset_FFS", "value" : "D:\\\\Data\\\\FME\\\\FME%20Server\\\\Data\\\\LDR\\\\1_Secties\\\\*.ffs" }, { "name" : "FANOUT_DIRECTORY", "value" : "D:\\\\Data\\\\FME\\\\FME%20Server\\\\Data\\\\LDR\\\\4_SectiesMetStationing" }, { "name" : "DestDataset_MSSQL_ADO", "value" : "GPL" }, { "name" : "MSSQL_ADO_OUT_SERVER_MSSQL_ADO", "value" : "GUHQTSQL1282\\\\TDBMSA" } ], "subsection" : "REST_SERVICE" }'

When changing the parameter type to tekst, it works fine. However, that deprives us from entering valid series of filenames.

2 replies

mark2atsafe
Safer
Forum|alt.badge.img+43
  • Safer
  • August 31, 2016

Hi @helmoet

I don't see any existing reports about this, but I've no doubt you are right. Can you file a case with our support team? See safe.com/support - then someone will be able to confirm the problem and let you know when a fix might be available - and if there is a workaround.

Apologies for any inconvenience this is causing

Mark


helmoet
Forum|alt.badge.img+8
  • Author
  • October 20, 2016
Aha I see now. I have to put an extra pair of square brackets around the parameter value in the REST call's upload body. Then it works fine.

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