Electronic Invoicing Service- How to override native GUID folder path for Azure Blob destination?

(2) Share

Report

Posted on by Sana Hammami

119

Hello Everyone,

I am configuring an Electronic Invoicing feature.

The functional requirement is the following: the output file generated from an action defined in the processing pipeline must be dropped directly into a specific folder tree inside our custom Azure Blob Storage.

Limitations encountered:

Via the e-Invoicing Processing Pipeline :
We used the standard Save document action targeting our custom data channel (connected via Key Vault and SAS token): =>The system automatically forces the creation of a folder path containing Tenant and Environment GUIDs (flux/<Tenant-GUID>/<Environment-GUID>/...) and mandates encapsulating the output inside a .zip file wrapper.

Any guidance on how to override this native path and compression behavior would be highly appreciated.

Categories:

Dynamics 365 Finance

Microsoft Dynamics AX

Dynamics 365 Project Operations

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Suggested answer

Aymen CHELBI 648 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hello @Sana Hammami,

I think, the right approach depends on your Approved Platform (PA).

-Scenario 1 : Your PA is EDICOM
Do not use Save document → Blob for the outbound flow. Replace it with:

Integrate with Edicom (configured with your Service ID, Group code, and Auth token from Key Vault)
Waiting for response from Edicom
Process response

The file is submitted directly to https://ipaasgw.edicomgroup.com , no Blob involved, no path or compression issue.

Scenario 2 : Your PA is not EDICOM, or you have a parallel deposit requirement
-For me the best workaround is a post-processing Logic App triggered on Blob creation: let the pipeline write to the forced path, then extract the .zip in memory and rewrite the file to your target folder (If your PA accepts SFTP, you can push directly from the same Logic App)

Best regards,

Aymen CHELBI

Was this reply helpful? Yes No
Nikhil More on at

Like
a
(1)

Report
Copy link

Link copied!

Hello @Sana Hammami,

Check if following document is helpful for you. ER Destination.

Electronic reporting (ER) destinations - Finance & Operations | Dynamics 365 | Microsoft Learn

We have used this setup for Generated Bank Files to be stored in Azure Blob Storage in particular folders.

Thank you,

Nikhil

Was this reply helpful? Yes No
Sana Hammami 119 on at

Like
a
(1)

Report
Copy link

Link copied!

@Nikhil More

Thank you for your reply , However, there isn’t an option to specify a custom blob storage destination for file uploads. Currently, files are always saved to the default Microsoft Azure Storage, with no apparent way to redirect them to a custom blob storage

Was this reply helpful? Yes No
Verified answer

Alireza Eshaghzadeh 15,225 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Sana Hammami

The ER destination setup and the Electronic Invoicing Service “Save document” action are not the same thing.

For the Electronic Invoicing Service processing pipeline, the Save document action writes the generated document package to the configured data channel. The folder structure that includes tenant/environment GUIDs and the ZIP package behavior is controlled by the Electronic Invoicing Service. As far as I know, there is no standard parameter in the feature setup to override that native folder path or force the service to drop only the raw XML directly into your own custom folder tree.

The ER destination article shared earlier is valid for normal ER output destinations in D365FO, but it will not override the internal Save document behavior of the Electronic Invoicing Service pipeline.

Was this reply helpful? Yes No