Hi,
I have a strange situation and can't figure out how it is caused.
Our application can store documents in Azure files or on a file share based on a configuration setting.
When a user uploads a document it is stored based on the physical filename and when not unique, Thinkwise adds a timestamp to the name.
After the user has uploaded the document it resides at a temporary location. Using a process flow we determine the actual, unique filename based on some pattern defined in the application and then we move the document to it's definitive location (another sub folder) with it's newly determined filename. To place the document in the definitive location we use the move file connector. The origin and target locations are of the same storage type (from Azure files to Azure files or from a file share to a file share).
When we execute this logic for a fileshare based document, it works as expected. The document is placed in it's new location with the filename we specified. The file contents did not change.
When we execute this logic for an Azure files based document, it seems to work as expected and the document is placed in it's new location with the filename we specified. The document itself however is being corrupted when moving. It has the same size as the original but only contains <NULL> values.
It is unclear why this last situation occurs. Could it be a rights problem? (although the initial upload executes without any problem). I tried without specifying a subfolder, but the corruption remains. I have tried "New file" or "Overwrite file", but also no change (the generated filename btw always results in a unique filename which does not exists as a file).
Any ideas where I could look?
We are using Universal with 2024.1 as the backend
