Skip to main content

Delete Private AOT projects in AX 2012

This is a common problem since the old days. People leave projects in their private project and no one can get to it to clean it up.

In pre AX2012, it was a matter of selecting the utilElements and calling the AOTDelete method. I won’t go through it here.

In AX2012, it is all maintained in the model store.

Let see it in pictures.

Below are the projects you want to delete.

Proj2013-01-30_1514

You can see them in the SysModelElement table. It is in the system tables section.

PrivateProj2013-01-30_1513

I wrote a job to loop through and delete them. I had to

Code:
static void deleteAllProjectObjects3(Args _args)
{
/*
msdn.microsoft.com/en-us/library/bb190038(v=ax.10).aspx
*/

SysModelElement sysModelElement;
ProjectNode privatePn;
ProjectNode pn;
utilElementName shortName;
int len;
str preFix;

// Navigate to the Private projects folder.
privatePn = infolog.projectRootNode().AOTfindChild("Private");

preFix = curuserid()+'_';
len = strlen(preFix);


while select sysModelElement
where sysModelElement.ElementType == 38
//&& sysModelElementName like "*TestProj*"
{
// remove <userId>_ from the _projectName to get the name used in the Projects tree for a private project
if (substr(sysModelElement.Name, 1, len) == preFix)
{
shortName = strdel(sysModelElement.Name, 1, len);
}

// Get a reference to the project.
pn = privatePn.AOTfindChild(shortName);

pn.AOTdelete();
}
}



Disclaimer:


Use at your own discretion. No guarantees here.

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

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.