Link document attachments to Tier-1 environment after downloading them from Azure blob storage

(3) Share

Report

Posted on by CU09091357-0

600

After copying the database from a cloud hosted environment to tier-1 (UAT to Local), and after downloading manually the document attachments from Azure Blob Storage, I'm trying to reach these attachment from the system (UI of F&O).

I changed the ACCESSINFORMATION value column in DOCUVALUE table to the path of my local where the documents are present, but it didn't worked.

Even I tried to import a file into the local evironment through the system to see the path's value in the DOCUVALUE table, and it gave me http://127.0.0.1:10000/devstoreaccount1/documents/fileid (I know it's a local host but nothing led me to a result)

How can I access these files and see them normally in the system of my local enviroment?

All responses (6)

Answers (1)

Sort by

Martin Dráb 240,866 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

T1 environments use Azure storage emulator instead of the real Azure storage. The file system isn't the supported type of storage, therefore using a path like C:\... can't work (as far as I know).
CU09091357-0 600 on at

Like (0)

Report
Copy link

Link copied!

Martin Dráb thank you for replying, so do you have any idea what is the path that should lead me to the files, or at least move the files to this Azure storage emulator?
Martin Dráb 240,866 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Your screenshot shows what path you got when you uploaded a file through UI.

If you want to connect to the emulator directly, you can use Azure Storage Explorer, for instance.
CU09091357-0 600 on at

Like (0)

Report
Copy link

Link copied!

Martin Dráb thanks!
CU09091357-0 600 on at

Like (0)

Report
Copy link

Link copied!

I still didn't get able to resolve it, so if someone who already faced this kind of issue before can help, thank you.
Verified answer

CU09091357-0 600 on at

Like (0)

Report
Copy link

Link copied!

The issue was resolved by migrating the blob files with their metadata to the azure specified path using azure storage emulator