Folks,
I'm attempting to upload and process bank reconciliation files that are uploaded to the D365 tenant's Azure blob storage, but it seems like D365 is not able to process files that were not uploaded through D365.
I was inspired to take this approach after investigating how D365 sends manually uploaded files to its tenant Azure blob.
I'm able to do the upload part fine, via a Power Automate flow, Create block blob action
NOTE, I've removed the Storage account name from the screenshot:
The file is uploaded to the blob:
However, when I call the BankStatementImportBatch class and pass in the identifier, in the above example, XFxmY2..., D365 is not able to find the file, the call on line 118 in the below screen capture fails:
When debugging, the exception looks like the following, note, the screen capture has a different id than the one above.
This same logic works fine with files that are manually uploaded
Both manually uploaded and Power Automate uploaded files are in the same temporary-file container on the tenant Azure blob.
I thought that the id might have a length restriction, but varying the lengths does not matter.
Any ideas why Power Automate uploaded files are not visible to D365?
Thanks!
André Arnaud de Cal...
291,971
Super User 2025 Season 1
Martin Dráb
230,846
Most Valuable Professional
nmaenpaa
101,156