Skip to main content

Using the Dynamics Ax Office Add-in

Hi everyone, I have been playing around with some Ax 2012 stuff and I was testing the Office Add-in and I think it is preatty cool.

In order to use the Office Add-in it has to be installed with the Ax client and some settings needs to be made in the system as well.

Lets dive into how it can be done, this is how I tested this function and it can most certainly be done in different ways.

First I created a small query called MyCustTableQuery



Next step is to provide information about the query and expose it so we can use the query in our office application, my application of choice was Excel.

In Dynamics Ax 2012 go to Organization Administration> Setup> Document Management > Document datasources


Here it is possible to select a query or service, in my example I used the query. So here i added a new record of data source type Query and then I selected my newly created MyCustTableQuery. Now the query is ready to use in what ever office application we have as far as the Office add-in has been installed.

Next step is to use the query in Excel. On the Dynamics Ax tab in Excel select Add Data


Open the field chooser and drag the fields on to the Excel grid where you want to display the information.


Once done close the field chooser and refresh the data


And there you have it, customer information displayed in a simple way in Excel using the Office Add-in for Dynamics Ax.

I hope this is helpful and happy implementations of Dynamics Ax

Comments

  1. UnknownSeptember 20, 2012 at 10:50 AM

    To make the query able to post information back to AX you simply run the AXD wizard, add the class to a AIF service and add the service to the Document Data sources. :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Dynamics 365 for operations – Table extensions

Background Extensions are a new way to add functionality and custom code to the D365 system without changing the standard code. In fact, Microsoft has announced that edit standard elements like those that we have done in the past will not be possible after 2017. By using extensions, we can achieve the same result by simply extending the standard system => EXTENSIONS. To read more about the difference between overlaying and extensions follow this link https://ax.help.dynamics.com/en/wiki/customization-overlayering-and-extensions/#extensions Extending tables By using table extensions, we can create a new table that adds new fields, field groups, indexes, mappings, relations, methods, subscribe to event handlers and more. When extending tables we need to follow the naming rule as such: <TABLENAME><_Extension> the compiler understands the _Extensions suffix and knows that the table in question is extending a table from the standard system. This gives us access ...
Post a Comment
Read more

Plug-able Authentication in Microsoft Dynamics AX 2012

I have worked in many projects involving the Enterprise Portal for Ax ranging from version 2.5. One of the biggest issue for the end customer/user has been the ability to have a plug-able authentication for EP. This has been an issue for example for customers that have other portals based on Share Point as well as custom build ASP.NET web sites. All these portals are able to share the authentication with Single Sign On, SSO. But until now with version 2012 of Ax this has not been possible since earlier versions of Ax have only supported Windows Authentication. So in scenarios where you implement an EP site for a customer that has other portals and uses for example forms authentication, if you are not running Ax 2012 you have to have a special/dedicated log-on to EP. One of the biggest advantages is the fact that now external users do not have to be in Active Directory mixed up with all the internal users or located in an extra AD repository with all the administrative IT work l...
Post a Comment
Read more

Remove HTML code from strings

When you work for example with the presentations DAX adds some HTML comment code to the text stored in the database. This can cause the text on the web to be displayed in incorrect format. This also takes up space in the database and makes the database file grow larger. <!--AXAPTA  MarginWidth="0" MarginHeight="0" WebletName="WebLet700062029" Type="WebPageWeblet" -->TEXT There is a nice X++ function: just call Web::stripHTML( string ), which will return the string without the HTML tags
Post a Comment
Read more