Skip to main content
  • EN

Dear FMEers,

We are using the API to submit transformations and get jobs with the result when completed. This works fine but the numFeaturesOutput is always 0 even when features are written. Must be something simple but I can't find how to get this to work.

Using FeatureWriters in 2016.1.

And how can we put text in the Description Parameter?

Features written by a FeatureWriter don't count towards the total number of features written. They do show up in the log though.

If you look at the job log, how many features is reported as written at the end?

You can specify the description in the TMDirectives block of the API call used to submit your job, here's an example using json:

{
  "FMEDirectives": {},
  "NMDirectives": {
    "failureTopics": N],
    "successTopics":  ]
  },
  "TMDirectives": {
    "rtc": false,
    "description": "This is a description of my job submission",
    "priority": 100,
    "tag": ""
  },
  "publishedParameters": Â
    {
      "name": "MY_PARAMETER",
      "value": "1234"
    }
  ],
  "subsection": "REST_SERVICE"
}

Features written by a FeatureWriter don't count towards the total number of features written. They do show up in the log though.

Thanks, good to know.

 

 

Features written by a FeatureWriter don't count towards the total number of features written. They do show up in the log though.

Didn't have to wait long to learn something new today, thanks Hans. Sounds like it's something that Safe should look into.

If you look at the job log, how many features is reported as written at the end?

You can specify the description in the TMDirectives block of the API call used to submit your job, here's an example using json:

{
  "FMEDirectives": {},
  "NMDirectives": {
    "failureTopics": N],
    "successTopics":  ]
  },
  "TMDirectives": {
    "rtc": false,
    "description": "This is a description of my job submission",
    "priority": 100,
    "tag": ""
  },
  "publishedParameters": Â
    {
      "name": "MY_PARAMETER",
      "value": "1234"
    }
  ],
  "subsection": "REST_SERVICE"
}
This is what we have implemented succesfully. But now I want to ask server what it did. I do get the "status": "SUCCESS" but I would like some more info... So I am looking for a way to communicate back from server to my other application via the API so I can tell the user how many features were processed..

 

This is what we have implemented succesfully. But now I want to ask server what it did. I do get the "status": "SUCCESS" but I would like some more info... So I am looking for a way to communicate back from server to my other application via the API so I can tell the user how many features were processed..

 

Short of using your workspace to store the results somewhere and then letting your application read them back, I'm not sure that's possible.
Didn't have to wait long to learn something new today, thanks Hans. Sounds like it's something that Safe should look into.
I agree, especially if we start seeing more and more workspaces using FeatureWriters this becomes an issue. I have a workspace running on FME Cloud that writes to a temporary Excel file and then uploads it to Dropbox. Same issue: 0 features written...

 

 

Short of using your workspace to store the results somewhere and then letting your application read them back, I'm not sure that's possible.
That's good to know. I can stop smashing my face at the desk then, thinking I'm to stupid to find out how it works LOL.

 

 

I agree, especially if we start seeing more and more workspaces using FeatureWriters this becomes an issue. I have a workspace running on FME Cloud that writes to a temporary Excel file and then uploads it to Dropbox. Same issue: 0 features written...

 

 

I believe I heard a Safer say at the FME UC that they are working on this.

 

 

I believe I heard a Safer say at the FME UC that they are working on this.

 

 

I've created an idea for it (please vote)

 

 

Reply


Community Stats

30,159
Posts
114,480
Replies
37,805
Members
Terms & ConditionsCookie 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.