Here is an example on how to create a zip file for an attachment and sending a download link to the user.
First, the zip folder needs to be created. After that, file entries can be created inside the zip folder which hold the file information of the attachment by copying the attachment file information to the file entry.
The class “File” has a method called “SendFileToUser” which creates a download link of the zip file and sends the link to the user. The file is put into the temporary blob storage.
// Example of creating a zip file for a document attachment and sending a download link to the user.
public static void main(Args _args)
System.IO.MemoryStream zipArchiveStream = new System.IO.MemoryStream();
const str extensionZip = '.zip';
const str zipFileName = 'ZipDownload';
select firstOnly docuRef
where docuValue.RecId == docuRef.ValueRecId;
if (docuRef.RecId != 0)
// Creates the zip folder.
using (System.IO.Compression.ZipArchive zipArchive = new System.IO.Compression.ZipArchive(
// Creates the file entry in the zip folder.
System.IO.Compression.ZipArchiveEntry fileEntry = zipArchive.CreateEntry(docuValue.filename());
// Opens the created file entry and copies the binary file information of the original file to the file entry in the zip folder.
using (System.IO.Stream fileEntryStream = fileEntry.Open())
// Gets the file stream of the document attachment.
fileStream = DocumentManagement::getAttachmentStream(docuRef);
// Send a download link of the created zip folder to the user.
File::SendFileToUser(zipArchiveStream, zipFileName + extensionZip);
To import inventory dimension fields, Microsoft has implemented a map called “InventInventoryDimensionEntityFieldsMapping” which can be used in Data Entity mappings. This map needs to be added to the Data Entity under “Mappings” node and the fields between the map and the Data Entity fields need to be mapped accordingly.
Note: Not the fields of the datasource need to be mapped, but the Data Entity fields itselves. This means that you first need to include the InventDim table as a datasource to your Data Entity and drag the needed inventory dimension fields into your Data Entity fields.
Additionally, the method “mapEntityToDatasource” needs to be implemented with below code. Upon insertion or update, the specified inventory dimensions will be resolved and the InventDim record is returned.
public void mapEntityToDatasource(DataEntityRuntimeContext _entityCtx, DataEntityDatasourceRuntimeContext _dataSourceCtx)
case dataEntityDataSourceStr(SuppItemTableEntitym InventDim):
InventDim inventDim = this.InventInventoryDimensionEntityFieldsMapping:resolveInventDim();
Note: If a Data Entity involves more than one InventDim datasource (e.g. a Data Entity for the SuppItemTable table), then the mapping does not work. In this case, custom code needs to be written to map the fields correctly.
The form control “DimensionEntryControl” has a method called “parmEditableDimensionSet” which sets only a specific dimension set as editable. Thus, by excluding financial dimensions from the dimension set, it is possible to make specific dimension not editable.
First, a dimension set storage needs to be created. After that, each financial dimension will be added to the dimension set storage excluding the dimensions which should not be editable. At the end, the dimension set storage will be passed to the mentioned parm-method “parmEditableDimensionSet” which then only sets the dimensions in the dimension set storage as editable.
Below is an example which implements the code in the form event handler “OnInitialized” to make dimension not editable upon calling a form.
public static void SalesTable_OnInitialized(xFormRun _sender, FormEventArgs _e)
DimensionEntryControl dimControl = _sender.design().controlName(identifierStr(DimensionEntryControlTable));
DimensionEnumeration dimensionSetId = DimensionCache:getDimensionAttributeSetForLedger();
const str contractNumber = 'ContractNo';
const str contractType = 'ContractType';
dimensionAttributeSetStorage = new DimensionAttributeSetStorage();
while select dimensionAttribute
where dimensionAttribute.Name != contractNumber // Exclude specific dimension which should be not editable
&& dimensionAttribute.Name != contractType // Exclude specific dimension which should be not editable
where dimAttrSetItem.DimensionAttribute == dimensionAttribute.RecId
&& dimAttrSetItem.DimensionAttributeSet == dimensionSetId
As a result, the dimension fields “ContractNo” and “ContractType” are no longer editable on the sales order form.
You might ask yourself why this blog exists. Well, to be honest, it exists to give me the possibility to document whatever I’ve developed in and for Dynamics AX and Dynamics 365 for Finance and Operations. It also serves as a Know-How database by collecting all my experiences and knowledge about Dynamics AX/365 and all other things around it. A good side-effect is that you can also profit from it 🙂
My goal is also to help out others by sharing my knowledge and also giving a platform to discuss about all the stuff around it.
My last reason: since I’ve already come across so many sites and blogs where people’s posts helped me out so much, I also want to give that back 🙂
Please enjoy your stay on my blog and feel free to contribute to the DAX/D365 community by commenting and sharing your thoughts/knowledge!