Unanswered question

I have a parameter with paths to the correct files and want to loop over them. When using the hardcoded path, there's no problem but once I start replacing the path with variables the file is no longer sent along.I've used the "filename" to check for the validity of the path but couldn't spot any mistakes here.Could you maybe help me? Do you need any more information?

I've tried using this but the "custom resources" point to a different location.They point to "C:\Users\User\AppData\Roaming\Neotys\NeoLoad\v5.3\custom-resources". In this file there are no files available.In my project, there also is a file called "Custom-resources", with the files that I'd like to use, but this file is ignored.

So adding the "${NL-CustomResources} didn't help sadly. Anything else I can try?

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.

I've added the files directly to the custom-resources folder. Changed the URL to the one you described and ran the check again.There was no change in result. I've added more screenshots and the logfile of the check for you to verify. Hopefully this provides you with enough information.

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?

I am also facing similar problem what Geert is facing. I think this happens when we have controller, load generator and script is designed on same machine. In my case I need to save the response which is a file into a folder which then needs to be referenced from future requests. So I used ${NL-CustomResources} assuming it will store the file in the custom-resources folder my my project. However, if I print the path referred by above variable, it points me to the custom-resources folder in C:\Users\User\AppData\Roaming\Neotys\NeoLoad\v6.5\custom-resources. Is there a way I can force it to look for my project folder?

The contents of CustomResources is copied from the controller to the LG at playback time, the LGs customResources will always refer to its own location and not that of the project. You can still use it to save files to and access them later, each LG will have its own location that all the VUs running on that LG share. Other VUs running on a different LG will use the CustomResources folder on that LG and so on