Skip to main content

Import Project Activity Breakdown (Hierarchy)

I hope this is one of many import blog posts. No promises but I may look at the same written using the Data Import Export Framework to show a comparison.

To continue with the subject…

I wrote a job to import project work breakdown structure tree. The csv file is in this format.


Final outcome is like so.


The job code is below:
static void ImportActvities(Args _args)
AsciiIO asciiIO;
Filename filename;
NoYesId skipFirstLine;
Container line;
Dialog dialog;
DialogField dialogFileName, dialogSkipFirstLine;

int numProcessedRecords=0;

smmActivities smmActivities;
ProjTable projTable;
ProjActivity projActivity;
Hierarchy hierarchy;
HierarchyLinkTable hierarchyLinkTable;
HierarchyTreeTable rootHierarchyTreeTable, parentHierarchyTreeTable;

ProjId projId;
smmActivityNumber activityNumber, parentActivityNumber;
str name;
str parentElementNumber;

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

if (
filename = dialogFileName.value();
skipFirstLine = dialogSkipFirstLine.value();

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

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


if (skipFirstLine)
line =;

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

if (line)
projId = conpeek(line,1);
activityNumber = conpeek(line,2);
parentActivityNumber = conpeek(line,3);
name = conpeek(line,4);

projtable = Projtable::find(projId);
if (!projTable)
throw error(strFmt("Project %1 cannot be found", projId));

if (!activityNumber)
throw error(strFmt("Activity %1 cannot be found", activityNumber));

// if activityNumber is blank or activity can't be found then insert it
if (!smmActivities::find(activityNumber) && projTable)
//create root
hierarchyLinkTable = HierarchyLinkTable::findRefTableRecId(tableNum(ProjTable), projTable.RecId, true);

if (!hierarchyLinkTable)
//create Hierarchy record
hierarchy.Name = projTable.Name;
hierarchy.Description = projTable.Name;
hierarchy.HierarchyType = HierarchyType::Project;
//use the number sequence or the project id as the hierarchyId. I prefer to use the Project id.
//hierarchy.HierarchyId = NumberSeq::newGetNum(CompanyInfo::numRefHierarchyId()).num();
hierarchy.HierarchyId = projTable.ProjId;
hierarchy.IsActive = NoYes::Yes;

//create HierarchyTreeTable root record
rootHierarchyTreeTable = HierarchyTreeTable::insertRoot(hierarchy.HierarchyId, projTable.ProjId);

HierarchyLinkTable::insertHierarchyLink(hierarchy.HierarchyId, tableNum(ProjTable), projTable.RecId);
if (hierarchyLinkTable)
hierarchy = Hierarchy::find(hierarchyLinkTable.HierarchyId, true);

select firstonly rootHierarchyTreeTable
where rootHierarchyTreeTable.HierarchyId == hierarchyLinkTable.HierarchyId &&
rootHierarchyTreeTable.ParentElementNumber == '';

parentElementNumber = '';
//parentActivityNumber is specified then find the node as the parent
if (parentActivityNumber)
parentHierarchyTreeTable = HierarchyTreeTable::findActivityNode(tableNum(ProjTable), projTable.RecId, parentActivityNumber);
if (parentHierarchyTreeTable)
parentElementNumber = parentHierarchyTreeTable.ElementNumber;

if (!parentElementNumber) //if parentElementNumber is blank, then use root node
parentElementNumber = rootHierarchyTreeTable.ElementNumber;

//create hierarchy tree node or activity
//if activityNumber is specified then create smmActivities. Otherwise, create a node without an activity
if (activityNumber)
// create smmActivities record
smmActivities.ActivityNumber = activityNumber;
smmActivities.Purpose = name;
smmActivities.Category = smmActivityCategory::Task;
smmActivities.insertParentLink(smmActivityParentType::Project, projTable.RecId, true);

// create ProjActivity record
if (!ProjActivity::exist(smmActivities.ActivityNumber))

info(strFmt("%1, %2 Record Processed", smmActivities.ActivityNumber,smmActivities.Purpose));

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

Import dialog like so will appear.


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.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