XMLvalidator & space in XML Filename

Hey ​@inka, would you be able to share a screenshot or a sample workspace showing how you've set up the XMLValidator, along with the file/folder user parameter? I've been trying to reproduce the issue on my end but I'm not running into any problems validating against file names with spaces, it would really help to see your exact setup so I can mirror configuration! Happy to help, Kailin

Hi ​@kailinatsafe 

Thank you Kailin. I did something incompatible, so probably that is why the error can’t be reproduced. My mistake, sorry.

I can give you the screenshot with $(FME_SHAREDRESOURCE_DATA):

This is the error, when I try to validate a XML-file with a space:

unable to open primary document entity 'D:\ProgramData\Safe Software\FMEFlow\repositories/""D:\ProgramData\Safe Software\FMEFlow\resources\system\temp\upload\Afvanding\XMLValidator_dandas_test.fmw\48e9064f-1bd9-2150-9b30-0b91d30c0be7\Knude 2.xml""'

Hello ​@inka, did you manage to sort it out? I think the issue may be a fault of how the user / flow parameters are configured in the transformer. The FME_SHAREDRESOURCE_DATA resolves to the path of the Data folder under Resources in FME Flow (e.g. which maps to C:\ProgramData\Safe Software\FMEFlow\resources\data). This parameter lets workspaces reference shared data without hardcoding paths. In this case, I wonder if we accidentally set the value for FME_SHAREDRESOURCE_DATA in the Navigator and then are also pointing the fileurl_knude user parameter directly at the same location (opposed to using the flow parameter in the path), which is resolving into an invalid location. Can you tell me the value set for fileurl_knude?

Let me know if you are still having issues validating a XML file with a space in the name. Happy to help, Kailin.