Skip to main content

Create a custom data import export framework entity[AX 2012]

Previously I had created a simple job to import Ledger alias. This post I will look at doing the same with the Data import export framework.

There is no entity in the DIEF (Data import export framework) to import ledger alias. So, we have to create a new one.

You can follow the Microsoft technet article but I will show you some screenshots here.

http://technet.microsoft.com/en-us/library/jj933277.aspx

One big thing you will realise is that it isn’t that straight forward for a non-developer. But for a developer it should be relatively easy to create a powerful import entity.

1. Click on Data import export framework > Common > Custom entity wizard

Select or enter the table name – in this case it is DimensionAlias.

DA2013-06-17_1459

2. Suggested names and options are set. Leave the default.

DA2013-06-17_1500

3. You will get a message about ForeignKey relationships. Just click yes.

DA2013-06-17_1504

This will take some time. A few minutes.

4. You will get errors.

DA2013-06-17_1512

5. A private project will be created. In my case it didn’t create all the elements it was supposed to. But that's easy enough to finish off manually (my preferred method).

DMF2013-06-21_1941

6. Field group – If you have any generate methods. Then you have to setup a Field group for them. The suffix number you see will set the sequence

DMF2013-06-21_1937

7. Title fields – make sure you set the title fields. Otherwise you will run into some errors.

DMF2013-06-21_1939

8. DMF class required – writing code for all your generate methods.

DMF2013-06-21_1940

That is it. You are ready to set it up and start using it.

You can download the full xpo project and start using it. Hopefully this blog gives you an appreciation for Data Import/Export Framework.

Download the xpo project

Labels:

Popular posts from this blog

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

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())     {    ...
Read more

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line.   NOTE: ...
Read more