In this example I am trying to achieve the Dynamics Ax Document Handling by using files Drag & drop option of windows OS.

According to standard Ax, if we want to attach the documents to the customer records,

We need to select the customer and select the Document Handling icon from the toolbar on the form as shown in below figure. 

Then it will open another form, on that form we need to click on New button, it will open the window's browser to select the file.

In this example no need to do all the above steps,

Ø  Select the customer record fom Ax-Customers form, for which customer we want to attach the document.

Ø  Select the file to attach.

Ø  Drag the file and drop on the windows control as shown in below figure.

Find the document at the following path, to understand how this example is implemented for the Customers.

http://cid-f2ec589e221a4db0.skydrive.live.com/self.aspx/.Public/DynamicsAx%20Utilities/Dynamics%20Ax%20Doc%20handling%20using%20Drag%20n%20Drop%20option.docx

... Cool ....

In this example, I am storing XML file as Resource under AOT of Dynamics Ax.

Find the related jobs at the following path, this path contains two jobs for

1)      Creation of new resource file.

2)      Reading the same resource as file.

http://cid-f2ec589e221a4db0.skydrive.live.com/self.aspx/.Public/Resource%20nodes%20as%20Metadata/Resource%20nodes%20as%20metadata%20xpos.zip 

For this article I got basic inputs from one of my previous colleague Santosh blog and also from MS employee Dilip (DaxDilip) blog.

Thanks to both of you.

When we are developing the workflow for EP in Dynamics Ax 2009,

We won’t find the workflow related control on the Tool box list, as we are finding other controls like AxGridView etc.

For this explicitly we need to add the Markup tags to the control.

Select the AxUserControl, right click and select the View Markup

Add the following lines in the markup view (change the properties accordingly as your scenarios)

<%@ Register Assembly="Microsoft.Dynamics.Framework.Portal, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"

    Namespace="Microsoft.Dynamics.Framework.Portal.UI.WebControls.Workflow" TagPrefix="dynamics" %>

<dynamics:AxWorkflowActionBar ID="WorkflowActionBar" runat="server"

    DataMember="ProjProposalJour_Current"

    DataSourceID="dsEPProjProposalInfo"     onworkflowworkitemactioncompleted="WorkflowActionBar_WorkflowWorkItemActionCompleted" />

<dynamics:AxDataSource ID="dsEPProjProposalInfo" runat="server" DataSetName="EPProjProposalInfo" />

Observe form the above markup tags AxWorkflowActionBar and AxDataSource are connected using AxDatasource ID. (Properties mentioned in green color)

To implement the methods related to workflow control in the code behind sheet (in Actual C# code sheet), add the following line.

using Microsoft.Dynamics.Framework.Portal.UI.WebControls.Workflow; 

For more details and how to implemnet the worklfow for EP pages, go through the following link. 

http://blogs.msdn.com/solutions/archive/2008/07/30/using-microsoft-dynamics-ax-2009-workflow-controls-in-ep.aspx

.....     ....   

In some scenarios, in a single web page we need to Hide/Show the certain web parts based on the user profile.

By using the following code snippets we can Hide the web parts of the page.

This example is for Hiding

1)      AxToolbarWebPart

2)      AxUserControlWebPart

Hidding the Toolbar

private void hideWebMenuToolBar()

    {

        WebPartManager webPartManager = WebPartManager.GetCurrentWebPartManager(this.Page) as WebPartManager;

        AxToolbarWebPart toolBarWebPart;

        for (int i = 0; i < webPartManager.WebParts.Count; i++)

        {

             toolBarWebPart = webPartManager.WebParts[i] as AxToolbarWebPart;           

            if (toolBarWebPart != null && toolBarWebPart.WebMenuName == "TmCustomers")

            {

                toolBarWebPart.Hidden = true;

                break;

            }    

        }

    }

Hidding the User control webpart

    private void hideWebPart()

    {

        WebPartManager webPartManager = WebPartManager.GetCurrentWebPartManager(this.Page) as WebPartManager;

        AxUserControlWebPart webPart;

        for (int i = 0; i < webPartManager.WebParts.Count; i++)

        {

            webPart = webPartManager.WebParts[i] as AxUserControlWebPart;

            if (webPart != null && webPart.ManagedContentItem == "TmMattersGrid")

            {

                webPart.Hidden = true;

                break;

            }

        }

    }

While working on EP (Browsing the pages) – encountered with the Unexpected ERROR.

Error: An error occurred during the processing of . Could not load file or assembly 'Microsoft.Dynamics.Framework.Portal, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Some time back also found similar kind of error in Ax client also, while deploying the pages in to the AOT

Error: Cannot add the specified assembly to the global assembly cache: Microsoft.Dynamics.Framework.Portal.dll

Then I had checked in the Windows\Assembly path, and observed that Microsoft.Dynamics.Framework.Portal.dll is missed.

Tried for copy and paste this .dll from Client\Bin folder to Windows\Assembly folder, it didn’t work.

Solution: Did the drag and drop Microsoft.Dynamics.Framework.Portal.dll from Bin folder to assembly folder.

After this drag and drop solution, EP is running without error.

This example is for displaying the Tree View control of ASP.Net by populating the customer details, in Dynamics Ax 2009 EP.

For populating the data on the tree control, I had taken the help of Proxy methods concept in EP.  I had implemented one method on the CustTable.

public static CustTable getAllRecords()

{

    CustTable   custTable;   

    Select * from custTable where custTable.CustGroup == "20";

    return custTable;

}

The same method, I am calling in EP by using Proxy like as follows,

IAxaptaRecordAdapter adapter = Microsoft.Dynamics.Portal.Application.Proxy.CustTable.getAllRecords(this.AxSession.AxaptaAdapter);

We can get the IAxaptaRecordAdapter object in other ways also, in this application I am receiving the same by using Proxy method concept.

For code and design the application, find the document at the following location

http://cid-f2ec589e221a4db0.skydrive.live.com/self.aspx/.Public/Dynamics%20Ax2009%20EP/Tree%20View%20Control%20example%20in%20Dynamics%20Ax%202009%20EP.docx

.......    

This might be the known issue, but we suffered little bit, while working on SL1 and BUS features, and we resolved this issue after lots of research. I want share this experience with my blog readers.

My Issue is:

We are working for a client in BUS layer and my client suggested some features from SL1 and told us to do the customizations for SL1 features according to our functionality.

So we installed SL1 on top of BUS layer, we are trying to work on that SL1 functionality, but we are not.

We installed the same SL1 in standard version of Ax also (no BUS.aod’s in this one); in that environment we are able to use the SL1 functionality, but where as in SL1 + BUS dev environment we are not able to use the SL1 functionality.

After lot of research we found that most of the standard Ax objects are modified by the SL1 and Bus layers, due to this, SL1 functionality is overridden by BUS layer, because BUS is upper layer and SL1 is lower layer.

Then we had merged the SL1 functionality into BUS layer, after this we are able to use both the layers functionality.

The main reason behind this issue is, we didn’t get the Upgrade Checklist after we installed the SL1 on top of the BUS layer, because we marked the check box option for the Prevent Startup of the checklist, after initialization check list is completed successfully, when we did the Ax installation.

We didn’t see upgrade check list, so we thought, in SL1 they might have created all the new objects, like SYS layer objects, but after some research only we noticed that, they have done some customizations for Standard Ax (SYS layer) objects.

Testing of multiple web parts in EP development…

If we have a situation like, we want to host more than one web part in a single page, and we want to test that web parts before deploying into the SharePoint pages. [These web parts are like connected]

Assume that we have three web parts and we want to test that three web parts before deploying on to the same page

In our Development web parts - Visual studio solution, Move to the Design view of AxWebPartPage.aspx. We will find a control for testing a single web part.

Now move to source view of the same page, we will find the following lines of code for that control.

<dynamics:AxUserControlWebPart ID="AxUserControlWebPart1" runat="server"

                        ManagedContentItem="CplTmConflictSearch" />

Copy that control source code and paste it two times as follows and change the ManagedContentItem property according to the name of the web part names.

<dynamics:AxUserControlWebPart ID="AxUserControlWebPart2" runat="server"

                        ManagedContentItem="CplTmConflictSearchGrid" />

                        <dynamics:AxUserControlWebPart ID="AxUserControlWebPart3" runat="server"

                        ManagedContentItem="CplTmConflictSearchRelationGrid" />

Here I am testing that three web parts by using three controls of AxUserControlWebPart.

Now run the solution, we can see the result in browser direclty; if it is success then we can deploy these web parts onto a single EP page.

This way we can test multiple web parts of the same page.

Dynamics Ax EP Web Parts Communication (Without using Share point connection)

                                dataSource.GetDataSet().DataSetRun.AxaptaObjectAdapter.Call("filterCustomerId", parmList);

                                break;

                            case "2":

                                dataSource.GetDataSet().DataSetRun.AxaptaObjectAdapter.Call("filterCustomer", parmList);

                                break;

                        }

                        dataSource.GetDataSet().DataSetViews[0].Research();                       

                    }                 

                    break;

                }

            }                       

        }

        catch (System.Exception ex)

        {

            AxExceptionCategory exceptionCategory;

            // This returns true if the exception can be handled here

            if (!AxControlExceptionHandler.TryHandleException(this, ex, out exceptionCategory))

            {

                // The exception is system fatal - in this case we re-throw.                                   

                throw;

            }

        }            

}

........

I am very Happy to say all my blog readers, my blog has completed one year. I started my blog (July 10^th, 2008).

I started my blog with the motivation from one of my colleague in my previous tenure.

He suggested me to; you are doing so much why you don’t share these things with others, you can share these things with others by writing your experience in to the blogs…..Which brought me into blogging in the first place. So far the journey has been really good...

By keeping this enthusiasm in sharing the information, I will update my blog with all my learning’s and my experience.....

I would like to thank all the people who visited and read my blog...

Simple and easy steps in Dynamics Ax 2009 EP Development:

Here I want to give simple steps for EP Development in Dynamics Ax 2009.

1)      Create the EP web user control in VS.Net and deploy the same in to Dynamics Ax. (Already we have so many articles, How to develop web parts in VS.net For Dynamics Ax2009 EP and how to deploy them in to Ax)

2)      In Share point portal create an .aspx page for the above web control and add it to EP.

3)      Create a new web menu item for the above .aspx page in Dynamics Ax.

AOT à Web à Web Menu Items àURL right clicks and selects New URL.

4)      Set the properties of newly created URL àprovide that .aspx page path and give the required properties also.

5)      Now right click on that new URL and select Import option, and then Page Definition will be imported into the AOT.

AOT à Web à Web Files à Page Definitions under this we can observe our newly created Web Menu Items page.

6)      Save the web menu item.

7)      Create a new web menu and drag the above web menu item to this new web menu or drag the above web menu item to the existing web menu.

8)      Here 4, 5, 6 and 7 steps are called Quick launch i.e. creation of web menu items and web menus.

9)      Also these steps (4, 5 & 6) are called as Add Pages to navigation.

         ...........     

Error: Could not find default endpoint element that references contract 'CustomerService.CustomerService' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element.

I had come across this error, while accessing the Dynamics Ax – AIF – Customer service from .Net windows user control.

Work around, to solve the above error:                                                     Reference from #MSDN

using System.ServiceModel;

//Configures the security settings of a basicHttpBinding binding.

                System.ServiceModel.BasicHttpBinding binding =

                new System.ServiceModel.BasicHttpBinding(BasicHttpSecurityMode.TransportCredentialOnly);

                binding.Name = "BasicHttpBinding_CustomerService";

                binding.HostNameComparisonMode = HostNameComparisonMode.StrongWildcard;

                binding.Security.Mode = BasicHttpSecurityMode.Message;

                BasicHttpSecurity mySecurity = binding.Security;

                mySecurity.Transport.ClientCredentialType = HttpClientCredentialType.Windows;

                mySecurity.Mode = BasicHttpSecurityMode.TransportCredentialOnly;

                mySecurity.Message.ClientCredentialType = BasicHttpMessageCredentialType.UserName;

                HttpTransportSecurity transSec = mySecurity.Transport;                           

                EndpointAddress endpointAddress = new EndpointAddress("http://ban-srv-ax.digimakerbengaluru.com/MicrosoftDynamicsAXAif50/customerservice.svc");

//Calling the Ax Service by passing the Binding and endPoint Address object, becuase, while calling this

//web service from user control we are not able to find the endpoint address of the service.

//i.e. It's not able to read out the exact endpoint address from config file.

    CustomerServiceClient   myCustomerService = new CustomerServiceClient(binding, endpointAddress);

                EntityKey[] custAcc = myCustomerService.create(cust);

                MessageBox.Show("Created the customer and CustomerId is:" + custAcc[0].KeyData[0].Value, "Customer");

This is work around. In case we are able to access the CustomerService from IIS, but we are not able to create the proxy object for accessing the service in C# project.  

Wow… Now we have a complete video session for the development of Enterprise Portal in Dynamics Ax 2009.

Here we can find that link from channel9

Dynamics AX Enterprise Portal Development Webinar – Recording

http://channel9.msdn.com/posts/diwakarb/Dynamics-AX-Enterprise-Portal-Development-Webinar/

Thanks to Microsoft EP Team.

AxD class Development – Security Key Issue:

If we are developing the new AxD class and that AxD class we want to use through Web Services.

Make sure that Service node of that corresponding AxD class has appropriate security key, otherwise the Services from that AxD class will not available for the end user.

Dynamics Ax will throw the following error from this place Path: \Classes\AifRequestProcessor\verifyRequestIsAllowed  -- Line no.7

Error: The user 'santo' does not have access to the service 'HNDWebLoginElementsService'.