Getting ApplicationSchema not set error in XSD Driven XML Writer

Hi ​@hasant1973, thanks so much for your question! It sounds like the issue may be occurring intermittently. Hopefully, with a bit more information, we’ll be able to narrow down the cause.

• Could you please share which version of FME Form you’re using? (You can find this under Help > About FME Workbench.)
• When the feature type error dialog box pops up, are any error messages printed to the logfile?
• Also, can you confirm whether the XML document your reader is pointing to is located in the same directory as the XSD file?
• Lastly, out of curiosity, have you noticed the same behaviour when using one of the AIXM Writers? That might be a quick workaround while we look into a more permanent fix.

Hopefully this provides some suggestions and could give us more info to investigate. If this is an urgent issue for you perhaps you could provide this same information in a support ticket, you can submit new requests here.

Hi ​@evieatsafe 

The Version is 2022.2.5.

The Log file contains:

Worker 23052 > R_1: At least of one the "Application Schema:" and/or "xsi:schemaLocation:" parameters must be set
Worker 23052 > An error has occurred. Check the logfile above for details
Worker 23052 > Failed to read schema features from dataset 'FEATURE_PATHS' using the 'XSD_DRIVEN_XML' reader

The XSD and the XML file are not in the same place. Since there is no single XSD I have a main.xsd that import many other XSDs (20+). The outfile needs to go somewhere totally different. 

I’m not using the AIXM Writers directly because they only support the first level of properties of AIXM. If you want to go deeper into the AIXM structure you are lost. The XSD Driven XML Writer is supporting all Features / Objects / Properties of AIXM. 

One more information for you: 

Maintaining the feature path string outside of FME, with a simple text editor, and inserting the prepared string into the FEATURE_PATHS attribute works fine. The XSD Driven XML Writer picks up the changes done on the FEATURE_PATHS and writes the XML properly. I guess the only part of FME that freaks out is the visual component who is going to show the feature tree for configuring the FEATURE_PATH by clicking on the items. 

Thanks for your answer. 

Hasan

Hi ​@hasant1973 sorry for the delayed response! I think we need to investigate further and reproduce this behaviour to be able to help resolve this. If you can please submit a ticket so that our team can look into this further, that would be great!

When submitting your ticket, please provide the following (if available):

• Any relevant screenshots (e.g. errors, configurations, etc.)
• Please provide a sample of the source data used in your workspace and an example of your file structure
• The workspace (or sample workspace) that you are encountering issues with. Please be sure to include any required data or custom transformers needed. If, possible please send this as a template (.fmwt).

Thank you for your patience as we investigate this together!