Skip to main content
  • EN

I've always had a hard time with XMLUpdater, but it usually ends up working.

This time I just can't make sense of the errors and how to solve it.

I have two XML, I want to take elements from one of them and use those elements to replace the elements in the other XML.

 

If I take the exact text from the XML-fragmenter at create an attribute containing just that, the XMLUpdater accepts it and produces the expected result.

If the XMLUpdater is part of the same flowpath as the XMLFragmenter the XMLUpdater will throw an error.

I even tried putting it into a new attribute with different datatype.

 

Can that be right??

 

The attached workspace is made in FME 2023.2 but the error is the same in FME 2022.2.

Any help or ideas is appreciated.

Hi @mathiku​ ,

This setting could work for you.

  • Update Type: Replace
  • Value: fme:get-xml-attribute("Assortments")

See also the screenshot.xmlupdater-parameters

Hi @mathiku​ ,

This setting could work for you.

  • Update Type: Replace
  • Value: fme:get-xml-attribute("Assortments")

See also the screenshot.xmlupdater-parameters

Thank you, I'm afraid it doesn't change much. I get different versions of the same errors.

Did you check the workspace? I'm curious about how this makes sense, to me it looks like a result of how FME handles the data(pointers) under the hood.

Thank you, I'm afraid it doesn't change much. I get different versions of the same errors.

Did you check the workspace? I'm curious about how this makes sense, to me it looks like a result of how FME handles the data(pointers) under the hood.

I think the attached workspace generates your desired result.

I saved this workspace with FME 2023.0.

Thank you, I'm afraid it doesn't change much. I get different versions of the same errors.

Did you check the workspace? I'm curious about how this makes sense, to me it looks like a result of how FME handles the data(pointers) under the hood.

I see it works. But the only tiny difference is that you specify read-method using 'fme-get-xml...'. Thanks so much for the help, but I feel like this is something Safe should fix.

Reply


Community Stats

30,611
Posts
115,987
Replies
38,248
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.