Access denied for local file system

Hi Mark,

Indicium handles the Write file process action and is not able to write to your Local drive. Indicium can only write to locations it has access to. To "Write” a file to your local drive, I suggest using the Download file process action.

Hi Mark.

I have tried using the download file, which works when a user selects a storage location themselves, however the flow is a system flow. Therefore, the download file doesn't fit the purpose of the flow.

The flow is generating documents and when successfully generating a document, the document should be saved on a specific path on a file storage location. One of the problems is that the file storage location (Accept environment) is not accessible from the DEV environment. The dev environment is hosted on Azure. That is the reason I wanted to use my local C:/ so the flow would use a similar way of working compared to the accept environment.

Do you have a suggestion to get a similar way of working for the DEV environment, which would use a write file process action?

Kind regards,

Mark

Ah, understandable. The Write file process action has to write to an accessible location, a location which is accessible by Indicium itself. If you want to use a Disk location, Indicium needs to have read/write rights for this location. Alternatively, you could use something like Azure blob storage.

Writing to your own local disk on your machine could truly only work if Indicium has access to that location, which most likely is not the case. Perhaps a OneDrive folder can be created, and OneDrive can then synchronize the content of the folder between you and the Indicium OneDrive folder.

My suggestion would be to have a File storage location similar to the one in the Acceptation environment, specially for the Development environment. Whilst it may cost money, the added benefit is that you are developing solutions using a similar setup as in Acceptation and Production.

I'll try and figure out how the OneDrive folder could  help with this problem. 

Unfortunately, that is how the environments are set up by the client. But that is most definitely something that would help and would be needed in the future. 

I do have an additional question about the write file process action. The documentation states that the target file name should be a relative path. I my system flow the file path could vary. For instance, the write file should be able to write a file through multiple subfolders, for instance: Company X folder, Administration subfolder X, Cases subfolder X where the file should  ultimately be written to. Could this be specified in the relative path?

Relative path means only the part after the Base path.

So for instance, your base path is "C:\App_files\” (this is set up in the File storage location itself)

The Relative path in your case would be "company_X\administration_X\cases_X\filename.txt”

Indicium will then write the filename.txt file into the folder as

C:\App_files\company_X\administration_X\cases_X\filename.txt

The relative path name can be constructed using Processes logic for example based on other variables.

Hope this helps!

Thanks, it certainly does help. When I wrote write a file through multiple subfolders, I meant the write file would create mutiple new folders when a folder doesn't exist. So for example: the path is C:\App_files\company_1\administration_1\cases_2\filename.txt
 

The C:\App_files\company_1 part exists, but the \administration_1\cases_2\filename.txt doesn't. Would the folder administration_1 & cases_2 be created with a file in the in cases_2 map?