Skip to main content

Import ledger alias with a job [AX 2012]

I wrote a job to import the ledger alias in 2012. It is fairly straight forward if you have the DMF installed.

Create a csv file with the following:

LedgerAlias2013-06-17_1440

End result will be:

Ledger2013-06-17_1445

Code:
//Name,Type,company,Account alias definition,initial focus
//test,Shared,CEED,401100-CR_GEN1-OU_3566-Training,MainAccount
static void importLedgerAccountAlias(Args _args)
{
//dialog
AsciiIO asciiIO;
Filename filename;
NoYesId skipFirstLine;
Container line;
Dialog dialog;
DialogField dialogFileName, dialogSkipFirstLine, dialogCountryRegionId;

//tables
DimensionAlias dimensionAlias;
Ledger ledger;

//fields to import
DimensionAliasName aliasName;
DimensionAliasType aliasType;
LedgerName ledgerName;
DimensionDisplayValue accountDefinition;
str initialFocus;

int numProcessedRecords;
;

dialog = new Dialog("Import Ledger Account Alias");
dialogFileName = dialog.addField(extendedTypeStr(Filenameopen), "File name");
dialogSkipFirstLine = dialog.addField(extendedTypeStr(NoYesId), "Skip first line");

dialog.run();

if (dialog.run())
{
filename = dialogFileName.value();
skipFirstLine = dialogSkipFirstLine.value();

}

asciiIO = new AsciiIO(filename, 'R');

if (!asciiIO || asciiIO.status() != IO_Status::Ok )
{
throw error (strfmt("@SYS19312",filename));
}


asciiIO.inRecordDelimiter('\r\n');
asciiIO.inFieldDelimiter(',');

if (skipFirstLine)
line = asciiIO.read();


ttsBegin;
while (asciiIO.status() == IO_status::Ok)
{
line = asciiIO.read();

if (line)
{
aliasName = conpeek(line,1);
aliasType = conpeek(line,2);
ledgerName = conpeek(line,3);
accountDefinition = conpeek(line,4);
initialFocus = conpeek(line,5);

select ledger
where ledger.Name == ledgerName;

select firstonly dimensionAlias where dimensionAlias.Name == aliasName;

if (!dimensionAlias)
{
dimensionAlias.Name = aliasName;
dimensionAlias.AliasType = aliasType;
dimensionAlias.DimensionAttributeValueCombination = DMFDimensionHelper::generateDynamicDimension(accountDefinition);
dimensionAlias.LegalEntity = ledger.PrimaryForLegalEntity;
dimensionAlias.DimensionAttribute = DimensionAttribute::findByName(initialFocus).RecId; //find RecId for initial focus
dimensionAlias.insert();

numProcessedRecords++;
}
}
}
ttscommit;

info(strFmt("Imported: %1", numProcessedRecords));
}




This requires that you have the DMF installed on your environment.


If you are running R2. Make sure to have this fix as I am using the DMF dimension helper class.


http://domhk.blogspot.com.au/2013/06/data-import-export-framework-financial.html


Keep an eye on the next post. I will do the same with Data Import/Export Framework.

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !set.in(custTable))         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi