You should store the files that you would like to upload inside your project folder under the "custom-resources" folder.

Then in your request you can use ${NL-CustomResources} as relative path to point to your files.

For instance, it will be something like that: ${NL-CustomResources}/${FV_uploadFiles.File}

I'm not sure from your response if you tried it or not. ${NL-CustomResources} is indeed replaced by an absolute path on your LG. If you copy your files under your project folder under that "custom-resources" folder all the files will be copied into the LG under that path C:\Users\User\AppData\Roaming\Neotys\NeoLoad\v5.3\custom-resources. This is automatically done by NeoLoad.

That's why using ${NL-CustomResources}/${FV_uploadFiles.File} in your request should work.

You should not add your data folder inside that custom-resources folder. You just need to copy all your files inside that <project_folder>\custom-resources folder and then in your POST request use exactly that syntax: ${NL-CustomResources}/${FV_uploadFiles.File}

You do not have to take care about the path. It is expected to work like this whatever your load generators OS.

In the custom-resources folder i can see your file but with that file name: GR-test alt brexp.csv with blank space. But in the file that you are requesting in your URL the name is GR-testaltbrexp.csv without spaces.

Could you make sure that the name in your variable files are exactly the same that the files you copied in the custom-resources folder?

The best would be to avoid any blank spaces.

In your load generator, if you go into the absolute path that is replaced with the ${NL-CustomResources} variable, do you see your files?

All the files that are stored inside your project folder under "custom-resources" folder are synchronized to that absolute path replaced for that ${NL-CustomResources} variable.

You have the full path in your POST request.