Dynamics NAVAX

Hard to give this one a good title. I am going to show how you can use the the Data Import Export Framework to import straight tables. Remember in previous versions we used Excel to import into the tables. We will do something similar using the DIEF. 1. Create a new Target entity. Select Entity type = Table. Give it an Entity name. Select the Staging table (This is the actual table you want to import into). 2. Create a new processing group. Select the entity you just created. Select the source data format. Save the record. Click on the Generate source file button and the wizard will appear. Follow the wizard and generate a sample file. 3. Process the processing group (standard process of importing data using DIEF). Note: No validation is done. So you need to make sure your data is clean and do a post check as usual.

I had to prove a concept the other day to embed google maps in a form. A big of googling and some ideas that had to mash up. Create a form with an ActiveX control “Microsoft Web Browser”. On the init method after super call. Add this line. ctrlactiveX.Navigate(' https://maps.google.com.au/maps?q=1 St Georges Terrace, PERTH WA 6000+(This is a random place)&output=embed' ); Final result looks like this. Reference: Thanks to this blog. http://microsoft-dynamics-ax-erp.blogspot.com.au/2012/01/integrate-google-map-in-dynamics-ax.html Minor change I had to make was to figure out the URL parameters. By passing the output=embed, you get a pretty good result.

This below is a step by step to export data from an AX environment to another environment using the Data Import/Export Framework. Export from Source AX environment 1. Open the Source data formats form. Create a record and select AX type. 2. Open the Processing group form and create a new record. 3. Click on Entities button. Select your entities you want to export (Example below has Customers). 4. (Optional) You can click on the Select button to put a filter. 5. Go back the Processing group form and click the Get staging data button. This will bring up the following execution form. Click the Run. This will then pull data and place it in staging table. It will enable the buttons on the Processing group form. 6. On the Processing group form, click the Export to AX button. This will bring up a dialog, enter the file name and type. This will generate a dat and def file. Import into Destination AX environment (Option 1) We will import the file using dat/def. Other options t...

Today I want to write a brief on the different data formats that are available in the Data Import/Export framework. File The File format allows for text (ie. csv) types to be imported. ODBC ODBC format allows for SQL type queries to be used. Imagine writing SQL statement to pull data from another database. AX AX format allows for exporting data in dat/def format. This is a nice addition because it allows you to move data to another AX instance. In other words, this pulls the AX entity data into the staging table and then you export it. Then you go to your other instance of AX you want to import into. Import the dat file and then process it. Check out TechNet on the source data formats. http://technet.microsoft.com/EN-US/library/jj225596.aspx#DefineSource I will try to write a little bit more about the AX format at another time because that is confusing at first. Simply, think of it as your way of moving entities from one AX database to another database.

Small post today. Data Import/Export Framework came out the other week. See the link: http://blogs.msdn.com/b/axsa/archive/2013/03/13/microsoft-dynamics-ax-2012-data-import-export-framework-old-name-data-migration-framework-is-now-available-on-information-source.aspx Good to see the model is now in its rightful place in the fpk Layer. Not much has changed in terms of the menu and design concept. New format has been added. csv and odbc we know from previous but I haven’t explored AX format yet. That’s it for now. I will explore some more and post what I find.

You might or might not have noticed in AX2012 R2, the use of projects as an offset account type has been blocked. If you try and select it you get a message like this. This was intentionally done by Microsoft to avoid further critical issues. Specially certain scenarios causing ledger in balance. Now, you have to remember there are alternatives to this. You can still use it as the main account and then use something else as the offset account. Otherwise, do it as two lines journal. [No screenshot]

Product attributes is a great piece of functionality that was introduced in AX 2012. It allows you to set up and capture additional information against a product. I recently have taken it one step further to make it more visible and user friendly. At the moment it is hidden away on a form you have to open. In a similar fashion to the way financial dimensions work, where the controls dynamically show up on a fast tab. The attribute controls do the same. Here is a quick screenshot to show how powerful it can be. I got the field groups to work by using attribute groups (which is part of retail key). If you are looking for some info on product attributes have look at these links. http://technet.microsoft.com/en-us/library/hh227548.aspx http://www.slideshare.net/murrayfife/using-product-attributes-to-record-nutritional-information-part-1 http://dynamicscare.com/blog/product-attributes-in-ax-2012 This is one of many pieces of frameworks that AX 2012 provides. Its up to us to make ...