We are trying to get an existing SSIS package to work with Azure Blob storage. The issue is the FolderPath that we dynamically generate.
Our folder path is defined in a variable something like this:
@[$Package::BlobFolder] + "CATEGORY/" + @[User::FileDate] + "/SUBCATEGORY"
and then the file we are trying to upload is a parquet file so in the Flexible File Destination Editor we have something like this:
Folder Path: (which is generated from the variable)
ourfolderpath/category/08152023/subcategory
File Name:
ourfilename.parquet
However when it runs the system concatenates the two values like so:
ourfolderpath/category/08152023/subcategory\ourfilename.parquet
which of course doesn't work. Any ideas?
Note, here are a list of things we've tried already that didn't work.
- add a forward slash to the end of the FolderPath, result: it just does this /\
- add a backslash to the end of the FolderPath (this errors out and can't be saved)
- add two backslashes = \ (still blows up)
- replace all forward slashes with backslashes = does not work.
Updates at 2:30pm PST:
First I'd like to point out that the variable expressions I've posted above are just examples what they are like. The real ones are much more complex (for what reason I do not know)
Second, I would also like to point out, that this whole thing actually works in production. What we are trying to do is set up a development version which was apparently never done.
Third, we suspect that perhaps the error we are seeing is wrong and not in any way affected by the backslash. The theory is this:
A) Which slash is used for concatenation is determined by the environment detected at run time. If it detects a connection to Azure Blob then it uses a forward slash, if not then it uses a backslash (because this is on a Windows server)
B) We suspect the system is failing to connect, therefore when the error gets written it is written with a backslash since no connection was ever made to Azure making it seem as though the backslash was the problem when in fact it's something else entirely.
That's about where we are with it right now. No idea why the connection is failing (or if that is even the problem)