I figured it out in the end, the file was a .json and for whatever reason the get blob storage doesn't seem to be able to see what's inide these but when I changed it to csv (and kept the json formatting within) it worked.
Get blob content using path - seems to be getting the content type instead of the actual content
So I have a logic app which get's the content of a blob json and then writes it somewhere else.
Yesterday it worked perfectly and I was able to run a test without issues, however, which it ran on it's own today instead of getting the contents of the file I get the following:
{
"$content-type": "application/octet-stream",
"$content": "//8nASDA9C.... extremely long string of random characters .....HOIUsA"
}
Any idea what might be causing this?
It's not showing any warnings and the connection I'm using uses an access key (I have recreated the connection and it's still not having it it)
Azure Blob Storage
Azure Logic Apps
2 answers
Sort by: Most helpful
-
-
MayankBargali-MSFT 70,936 Reputation points Moderator
2023-03-10T06:23:50.4733333+00:00 @Lewis Kirk Thanks for reaching out. When you use Get blob content using path (V2) action then the return is binary content of the file. Depending upon whether you have configured true value for Infer content type then if the content of file can be infer then it returns the string content of the file else it returns the content-type of the file. Based on the content-type parameter you can now leverage the base64ToString to convert your base64 content to the string.