Skip to main content
Solved

How to get unzipping to work (status -7)?


I have been trying to get a test case working to use the Unzip action, but all efforts fail with a -7 status ( The 'File data' input parameter did not represent a valid .zip file.).

The flow is set up very simple:
- Upload file to Azure Blob storage (Task with a file upload);
- Use “Read file” action to get the binary data for the next step;
- Use “Unzip file”

The last step has the original filename “test.zip”, the binary data and a chosen target folder “unzipped_files”. The filename is confirmed to still be the same name at the upload location.
 

Test process flow

 

Input Unzip file
Partial shot of Unzip file action step

I have even tried setting all “Encoding” options at the “Read file” action in case that was necessary, but nothing seems to change the result.

The zip file contains is just 3 .jpg images and manually downloading the file from the storage location has given a working file that I can unpack without problem.

Any idea what could be wrong or missing?

Best answer by Erwin Ekkel

Are you using the latest indicium and universal versions? 

-7 means there is something wrong with the data parameter. Can you check the output parameter for the read file connector? It should look something like this:

 


When i look at my test the parameter is only giving back bytes, are you using a varbinary max as parameter?

 

 

View original
Did this topic help you find an answer to your question?

4 replies

Forum|alt.badge.img+17
  • Moderator
  • 766 replies
  • Answer
  • May 26, 2025

Are you using the latest indicium and universal versions? 

-7 means there is something wrong with the data parameter. Can you check the output parameter for the read file connector? It should look something like this:

 


When i look at my test the parameter is only giving back bytes, are you using a varbinary max as parameter?

 

 


@Erwin Ekkel I had applied the wrong domain to the File data output variable 😅. Changing it to the VARBINARY(MAX) did make it work.

So focused on the naming of the parameters, that I completely overlooked this.

Thanks a lot for your help!


Forum|alt.badge.img+17
  • Moderator
  • 766 replies
  • May 27, 2025

@Mark_Plaggenborg  there should have been a validation for this: 

 


However, I can imagine that when you work on a process flow you won’t run validations during this process. I will create an idea to have the data type checked during creation of the system flow. 


Since it was an experiment, I was indeed not busy with validations as I was limited to work only on this flow. The data type was set to NVARCHAR(MAX), which would not have triggered the validation in this case it seems. Testing with INT does make it fail.

I do appreciate the mention of the validation, so it reminds me to use it more often on flows just in case.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings