Export set - MID Server creates "export" folder in a strange folder structure

[Anish Reghu]

Dear experts,

During an exercise with the Export sets, we found that the files are getting exported, but the "export" folder sits within a strange folder structure. Please take a look at this path and kindly advise, why this is so.

C:\ServiceNow MidServer Dev\mid.rome-06-23-2021__patch1-08-26-2021_09-06-2021_0849.windows.x86-64\agent\export\

But we had set the File path to be as follows:

Why does the export folder then sit in the "mid.rome...." folder instead?

Which configuration is being read in ServiceNow at the backend to create the "mid.rome...." folder in the target MID Server Windows system? Is there any property? If yes, which backend script invokes that property?

During our discussions, I was also told that the File path configured is a relative path and the root path is configured at the backend somewhere else. If yes, where is it?

Regards,

Anish

[OlaN]

Absolutely!

So lets say your mid server agent is installed in this path:
C:\ServiceNow\
Then the base path for export files will become something like this:
C:\ServiceNow\agent\export\

Then in the configuration, were you type in the path for your export file, you might type in something like this:

\my custom path\export folder\

All this above will be added to the base path above, so the full path where the files end up will become:

C:\ServiceNow\agent\export\my custom path\export folder\

if you don't type anything at all in the file path, the files will end up in the same directory as the base path, but everything you type in as file path, will be created as a subdirectory to the base path on the server.

Hope this makes sense.