Skip to main content
Solved

XMLFragmenter Failing with SQL query

  • January 23, 2020
  • 7 replies
  • 7 views

Forum|alt.badge.img

I have the following that works

SDE DATA => Test Filter (Name = Point) > XMLFramenter > Rest works as expected 1 feature coming through

I want to remove the Test Filter and and put an SQL Where clause at the SDE Data level ( Name = Point ) the SQL is valid and 1 feature comes through however the XMLFramenter fails.

Looking at the data in both cases for the field that contains the XML data is identical yet it fails in one case and not the other, any ideas?

Best answer by tforward

I was able to fix the issue by putting an AttributeEncoder set to UTF-8 in front of the XMLFragmeter

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.

7 replies

ebygomm
Influencer
Forum|alt.badge.img+44
  • Influencer
  • 3427 replies
  • January 23, 2020

If you keep the test filter in even though it's now redundant, does it fail or pass?


Forum|alt.badge.img
  • Author
  • 24 replies
  • January 23, 2020

If you keep the test filter in even though it's now redundant, does it fail or pass?

Still fails


ebygomm
Influencer
Forum|alt.badge.img+44
  • Influencer
  • 3427 replies
  • January 23, 2020

Still fails

What is the fme rejection code?


Forum|alt.badge.img
  • Author
  • 24 replies
  • January 23, 2020

What is the fme rejection code?

There is not one, the data goes to the "rejected side" of the XMLFragmeter. If i look at this rejected data I can see the attribute with the XML data in it and as mention before is the same as when it works


ebygomm
Influencer
Forum|alt.badge.img+44
  • Influencer
  • 3427 replies
  • January 23, 2020

There is not one, the data goes to the "rejected side" of the XMLFragmeter. If i look at this rejected data I can see the attribute with the XML data in it and as mention before is the same as when it works

Hmm, I've always had a rejection code attached to the rejected record(s), e.g.


Forum|alt.badge.img
  • Author
  • 24 replies
  • January 24, 2020

Hmm, I've always had a rejection code attached to the rejected record(s), e.g.

I've edited the post to include the error log see attached above


Forum|alt.badge.img
  • Author
  • 24 replies
  • Best Answer
  • January 24, 2020

I was able to fix the issue by putting an AttributeEncoder set to UTF-8 in front of the XMLFragmeter