Skip to main content
Archived

XMLUpdater Usability Improvement #2

Related products:FME Form
rylanatsafe
siennaatsafe
runneals
mmccart
  • rylanatsafe
    rylanatsafe
  • siennaatsafe
    siennaatsafe
  • runneals
    runneals
  • mmccart
    mmccart

The 'Update Type' etc. required in the XMLUpdater is different depending on whether the XML tag already exists or not ('Replace Contents' or 'Insert' respectively). This makes it very awkward to deal with XML of unknown completeness.

There should be a way to create a tag , including all the hierarchy above it, if the tag doesn't exist and just 'Replace Contents' if the tag does already exist.

e.g.

Update TypeXML PathValue TypeValue
Insert or Replace Contents/metadata/dataIdInfo/idCitation/date/reviseDateXML/XQueryfme:get-attribute("_timestamp")

...should generate...

<metadataxml:lang="en">    <dataIdInfo>       <idCitation>          <date>             <reviseDate>20161116</reviseDate>          </date>       </idCitation>    </dataIdInfo> </metadata> 

...whether the starting document was


<metadataxml:lang="en"> </metadata>

or

<metadataxml:lang="en">   <dataIdInfo>      <idCitation>         <date>            <reviseDate>Yesterday</reviseDate>         </date>      </idCitation>   </dataIdInfo> </metadata>

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.

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