Typically we get a screenshot the root of the C: drive such as:

The question is a variation of:

We are getting XML files created at the root of the C drive. After deleting them and running SmartConnect integrations, they keep coming back.

What is causing this and how do we stop it?

There are 2 separate answers to this.

The first is: What causes the files to be created?

This is a function of the map option of the integration that is being run.

In the Map on the Options tab, the files are set to be created by marking the “Use Log” and “Log Xml” checkboxes.

If the destination for the integration is a Dynamics GP Destination, SmartConnect will log the XML document that is submitted to eConnect. This could be used as an alternative instead of setting the Destination to “Dynamics GP – File” as the output is the same.

Therefore, to stop SmartConnect from creating the files – unmark this checkbox.

The next is: Why are the files created at the root of the C: drive?

This is a non-obvious setting in the SmartConnect Setup window on the “Other Settings” tab.

The label for this field is “Error File Path” but it is also used for the destination folder when the Log Xml checkbox is marked.

I would suggest to not using the c: root as the path and switch it to something like c:temp or similar.  Ideally we’d be able to use an environment variable such as emp0ut in my testing that didn’t work – the XML files were not created.

One last tip. The name of the XML files created is determined as follows:

__

In the screenshot, I had files PMTRX_16_1, PMTRX_16_2, PMTRX_16_3.

These were generated by my map named PMTRX, on the 16thrun, and documents 1, 2, and 3 in the order they were created by SmartConnect.

Until next time,

Patrick
eOne Support
Have something you would like to see on our next Tech Tuesday? Email us at sales@eonesolutions.com with your request!