Data Import/Export Framework– Error: SysDictTable object not intialized

Recently I was importing Positions using the Data Import/Export Framework (staging to target process). I got the mentioned error.

After doing some debugging I found there was a table “PayrollPositionDetails” that was in one of the DMF tables “DMFTargetEntityHierarchy”. But the Payroll configuration key was turned off.
I ended up deleting the record from the DMFTargetEntityHierarchy table. (Alt+F9 to delete from table browser).

Reran the processing group and all worked.

Read more...

Install the Data import/export framework (DIXF, DMF) [AX 2012]

Note
The procedure for completing this task has changed for cumulative update 7 or later for Microsoft Dynamics AX 2012 R2. For more information, see the section later in this topic.

This topic describes how to install the Microsoft Dynamics AX 2012 Data Import/Export Framework.
Before you begin, your environment must include the following components:

• A running version of AX 2012 that has been configured for your business
  
• A running version of Microsoft SQL Server Integration Services that is running the same version of SQL Server that is hosting the Microsoft Dynamics AX business and model store database
  

Important
Because the staging environment is highly normalized and might require significant processing bandwidth, we recommend that you increase the Maximum buffer size setting for your environment while you migrate data. Use the Server configuration utility to set the value. For more information, see Tune data access settings.

Install the version of the Data Import/Export Framework that is available in AX 2012 R3

---

Components of the Data Import/Export Framework must be installed on computers that are running Integration Services, a computer that is running an instance of Microsoft Dynamics AX Application Object Server (AOS), and a computer that is running the Microsoft Dynamics AX client. You must run the installer locally on each computer.

Caution

If you have previously installed the Data Import/Export Framework from InformationSource, you must fully uninstall it and then reinstall it for cumulative update 7 for Microsoft Dynamics AX 2012 R2. As part of this full uninstallation, you must remove all binary files by using Add/Remove Programs and uninstall the Data Import/Export Framework model. For more information, see How to: Remove (Uninstall) a Model.

1. Start Microsoft Dynamics AX Setup. Under Install, select Microsoft Dynamics AX components.
   
2. Advance through the first wizard pages.
   
3. If the Setup Support files have not yet been installed on the computer, the Select a file location page is displayed. The Setup Support files are required for installation. Enter a file location or accept the default location, and then click Next.
   
4. On the Ready to install page, click Install.
   
5. On the Select components page, select the appropriate component for the computer that you are installing to, in the following order: server, AOS component, client component.
   
   1. The prerequisite validation check runs. Address any issues that the prerequisite check finds outside the installer, and then restart the validation check. When all prerequisites have been found, click Next.
      
   2. On the computer that is running SQL Server Integration Services, install the Data Import/Export Framework (DIXF) service.
      Specify a service account and the version of SQL Server that is running. We recommend that you use the AOS service account.
      
   3. On the AOS instance, specify the name of the server that is running SQL Server Integration Services.
      

Install the version of the Data Import/Export Framework that is available in cumulative update 7 for Microsoft Dynamics AX 2012 R2

---

Important
If you are running Microsoft Dynamics AX 2012 R2, we strongly recommend that you use the version of the Data Import/Export Framework that is available in cumulative update 7.

Components of the Data Import/Export Framework must be installed on computers that are running Integration Services, on a computer that is running an instance of Microsoft Dynamics AX Application Object Server (AOS), and on a computer that is running the Microsoft Dynamics AX client. You must run the installer locally on each computer.
The Data Import/Export Framework has been released as part of cumulative update 7. Therefore, detailed installation instructions are included in the Apply updates to database, AOS, and clients section of the Apply updates to database, AOS, and clients topic.

Caution

If you have previously installed the Data Import/Export Framework from InformationSource, you must fully uninstall it and then reinstall it for cumulative update 7 for Microsoft Dynamics AX 2012 R2. As part of this full uninstallation, you must remove all binary files by using Add/Remove Programs and uninstall the Data Import/Export Framework model. For more information, see How to: Remove (Uninstall) a Model.

Install the Data Import/Export Framework from InformationSource

---

Note
We recommend that you use the version of the Data Import/Export Framework that is available from InformationSource only with AX 2012 or Microsoft Dynamics AX 2012 Feature Pack.

Components of the Data Import/Export Framework must be installed on computers that are running Integration Services, on a computer that is running an AOS instance, and on a computer that is running the Microsoft Dynamics AX client. You must run the installer locally on each computer.
Download the installation package for the Data Import/Export Framework, DataImportExportFramework.zip, and extract the package to a local folder.

Install the Data Import/Export Framework on the computer that is running Integration Services

---

1. On the computer that is running Integration Services, right-click Setup.exe, and then click Run as administrator.
   

   Important
   If you do not run Setup as an administrator, the Data Import/Export Framework DLLs will not be copied to the correct locations or registered.

2. In the Setup wizard, accept the license terms, and then, on the Select components to install page, click Data Import/Export Framework service.
   
3. On the Prerequisite validation page, if the computer passes the validations that are required, click Next.
   If the computer does not pass the validations, install the prerequisites, and then restart Setup.
   
4. On the Specify a service account page, enter the same account that is used for the AOS service, and then click Next.
   
5. On the Select version of Microsoft SQL Server page, select the appropriate version, and then click Next.
   

   Caution
   This page appears only if Setup detects that versions of Integration Services for both SQL Server 2008 and SQL Server 2012 are installed on the computer.

6. On the Ready to install page, click Install.
   
7. On the Installation completed page, select Show logs to display the log files, and then click Finish.
   The log file is stored in the same location that Setup was run from.
   

Install the Data Import/Export Framework on an AOS instance

---

1. On a computer that is running an AOS instance, right-click Setup.exe, and then click Run as administrator.
   

   Important
   If you do not run Setup as an administrator, the Data Import/Export Framework DLLs will not be copied to the correct locations or registered.

2. In the Setup wizard, accept the license terms, and then, on the Select components to install page, click Application Object Server (AOS) component.
   
3. On the Prerequisite validation page, if the computer passes the validations that are required, click Next.
   If the computer does not pass the validations, install the prerequisites, and then restart Setup.
   
4. On the Specify SQL Server Integration Services location page, select the computer that is running the version of SQL Server Integration Services that you installed the Data Import/Export Framework service on, and then click Next.
   
5. On the Ready to install page, click Install.
   
6. On the Installation completed page, select Show logs to display the log files, and then click Finish.
   The log file is stored in the same location that Setup was run from.
   

Install the Data Import/Export Framework on a client

---

1. On a computer that is running a Microsoft Dynamics AX client, right-click Setup.exe, and then click Run as administrator.
   

   Important
   If you do not run Setup as an administrator, the Data Import/Export Framework DLLs will not be copied to the correct locations or registered.

2. In the Setup wizard, accept the license terms, and then, on the Select components to install page, click Client component.
   
3. On the Prerequisite validation page, if the computer passes the validations that are required, click Next.
   If the computer does not pass the validations, install the prerequisites, and then restart Setup.
   
4. On the Ready to install page, click Install.
   
5. On the Installation completed page, select Show logs to display the log files, and then click Finish.
   The log file is stored in the same location that Setup was run from.
   

Install the Data Import/Export Framework model

---

After all the components have been installed, you must install the Data Import/Export Framework model.

1. On the client computer, from the location where you installed the Data Import/Export Framework, import the DataImportExportFramework.axmodel file. For more detailed instructions, see How to: Export and Import a Model.
   

   Note
   Verify that the Microsoft Dynamics AX Management Shell is pointing to the database that you want to install the model in.

   1. Drain client connections to the AOS instance that you are working with.
      
   2. Stop the AOS.
      
   3. Use one of the following command-line tools to import the model.
      The version of the model that you import depends on the version of Microsoft Dynamics AX that you are running:
      
      • For AX 2012, install the model from the 2012 directory.
        
      • For AX 2012 Feature Pack, install the model from the 2012 FP directory.
        
      • For AX 2012 R2, install the model from the 2012 R2 directory.
        
      Windows PowerShell
      
      Windows PowerShell

      Copy

      Install-AXModel -File "C:\Program Files\Microsoft Dynamics AX 2012 Data Import Export Framework Client Component\<version number>\model\DataImportExportFramework.axmodel"
      

      AXUtil
      
      Copy

      axutil import /file: "C:\Program Files\ Microsoft Dynamics AX 2012 Data Import Export Framework Client Component \<version number>\model\DataImportExportFramework.axmodel"
      

2. Restart the AOS service.
   
3. Start the client.
   
4. In the Model store has been modified dialog box, click Compile and synchronize.
   
5. When the synchronization is completed, click Compile into .Net Framework CIL.
   
6. If the dialog box does not open by itself, follow these steps:
   
   1. Compile the application from System administration > Periodic > Compile.
      
   2. Click System administration > Periodic > Database > SQL administration. On the Table actions menu, click Synchronize database.
      
7. Compile into .NET CIL from System administration > Periodic > Compile.
   After the model has been compiled into .NET CIL, the Data Import/Export Framework button is added to the navigation pane.
   

Troubleshoot an installation of the Data Import/Export Framework from cumulative update 7 for Microsoft Dynamics AX 2012 R2

---

This section describes how to troubleshoot issues with a Data Import/Export Framework installation from cumulative update 7 for Microsoft Dynamics AX 2012 R2.

You receive an “Assembly containing type Microsoft.Dynamics.AX.DMF.ServiceProxy.DmfEntityProxy is not referenced.” error

---

After you slipstream cumulative update 7 for Microsoft Dynamics AX 2012 R2, the Data Import/Export Framework appears to be installed, but you receive error messages when many forms are opened.
Resolution
When you slipstream install cumulative update 7 for Microsoft Dynamics AX 2012 R2, the Data Import/Export Framework appears to be installed for members of the System Administrators role. However, the binary components of the framework are not present. To fully install the Data Import/Export Framework, you must run the update installer. For more information, see the "Apply updates to database, AOS, and clients" section of the Apply updates to database, AOS, and clients topic.

Troubleshoot an installation of the Data Import/Export Framework from InformationSource

---

This section describes how to troubleshoot issues with a Data Import/Export Framework installation from InformationSource.

The Data Import/Export Framework does not compile

---

After you install the Data Import/Export Framework, if you cannot compile, validate that the Data Import/Export Framework was installed correctly.

1. Verify that the Microsoft Dynamics AX Data Import/Export Framework service is running.
   
2. Verify that the Data Import/Export Framework DLLs are present in C:\Program Files (x86)\Microsoft Dynamics AX\60\Client\Bin folder:
   
   • Microsoft.Dynamics.AX.DMF.Mapper.dll
     
   • Microsoft.Dynamics.AX.DMF.PreviewGrid.
     
   • Microsoft.Dynamics.AX.DMF.ServiceProxy.dll
     
   • DMFConfig.xml
     
   • Microsoft.Dynamics.AX.DMF.DriverHelper.dll
     

Resolution
Copy the DLLs from the installation location (C:\Program Files\Microsoft Dynamics AX 2012 Data Import Export Framework Client Component) to the C:\Program Files (x86)\Microsoft Dynamics AX\60\Client\Bin folder.

Exception message while you use Data Import/Export Framework

---

While you use the Data Import/Export Framework, you might receive the following error message:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException
Verify that the following files are present in the C:\Program Files (x86)\Microsoft Dynamics AX\60\Server\Bin folder on the server that is running the AOS instance:

• DMFConfig.xml
  
• DMFClientConfig.xml
  
• Microsoft.Dynamics.AX.DMF.ServiceProxy.dll.config
  

Resolution
Copy the .xml and the config files from the installation location (C:\Program Files\Microsoft Dynamics AX 2012 Data Import Export Framework Server Component) to the C:\Program Files (x86)\Microsoft Dynamics AX\60\Server\Bin folder on the server that is running the AOS instance.

Changes to the location of the Data Import/Export Framework service

---

If you have to update the location where you run Integration Services and the Data Import/Export Framework service, you can update the endpoint address in the Microsoft.Dynamics.AX.DMF.ServiceProxy.dll.config file to use the new server name.
<endpoint address="http://<<NEW MACHINE NAME>>:7000/DMFService/DMFServiceHelper.svc"

Note
The Microsoft.Dynamics.AX.DMF.ServiceProxy.dll.config file is located in the C:\Program Files (x86)\Microsoft Dynamics AX\60\Server\Bin folder on the server that is running the AOS instance.

Read more...

AX2012 Import HCMWorker or Employee from CSV

AX2012 Import HCMWorker or Employee from CSV

This is the sample code for creating the Employee and if employee exists then updating the employee.
First build the class to read from CSV file and call this methods for creating/updateing the worker.
Please change the container column number values from your csv positions.

we can use HCMWorkerImportService for create, but this service did'nt provide the update functionality.
I will update the the next post using service to create/update the employee.

private void run()
{

 if (!HcmWorker::findByPersonnelNumber(conPeek(_c, #EmployeeNumber)).RecId)
        {//Update employee
            this.employeeCreate(_c);
        }
        else
        {//Insert employee
            this.employeeUpdate(_c);
        }

}


static public Description createDescription(DirPersonName _dirPersonName)
{
    #Define.Space(" ")
    return _dirPersonName.FirstName
        + (_dirPersonName.MiddleName ? #Space + _dirPersonName.MiddleName : "")
        + (_dirPersonName.LastName   ? #Space + _dirPersonName.LastName   : "");
}


public Static HcmPersonGender convGender(str _gender)
{
    HcmPersonGender ret;
    #Define.Female("Kvinde")
    #Define.Male("Mand")
    ;
    switch (_gender)
    {
        case #Female:
            ret = HcmPersonGender::Female;
            break;

        case #Male:
            ret = HcmPersonGender::Male;
            break;

        default:
            ret = HcmPersonGender::None;
    }

    return ret;
}


public Static str defaultCountryRegionId()
{
    str ret;
    LogisticsPostalAddress  logisticsPostalAddress_Default;
    ;

    logisticsPostalAddress_Default.initValue();

    ret = logisticsPostalAddress_Default.CountryRegionId;

    return ret;
}





public static date convDate(str _date)
{
    Date ret;
    ;

    ret = str2Date(_date, 123);

    return ret;
}


This method is used to create the employee.
Create
private void employeeCreate(container _c)
{
    boolean                                 ret = true;
    CompanyInfo                             companyInfo;
    HcmEmploymentRecId                      newEmploymentRecId;
    ValidFromDateTime                       employmentStartDateTime;
    ValidToDateTime                         employmentEndDateTime;
    HcmWorker                               newHcmWorker;
    DirPerson                               dirPerson;
    DirPersonName                           dirPersonName;
    HcmEmploymentType                       hcmEmploymentType = HcmEmploymentType::Employee;
    NumberSeq                               numberSeqPersonnelNum;
    HcmPersonPrivateDetails                 HcmPersonPrivateDetails;
    AxLogisticsPostalAddress                axLogisticsPostalAddress = new AxLogisticsPostalAddress();
    AxLogisticsLocation                     axLogisticsLocation;
    ;

    companyInfo = companyInfo::find();

    employmentStartDateTime = datetobeginUtcDateTime(HrmImportEmployeeMasterdata::convDate(conpeek(_c, #DateOfHiring)), DateTimeUtil::getUserPreferredTimeZone());
    employmentEndDateTime   = DateTimeUtil::applyTimeZoneOffset(DateTimeUtil::maxValue(), DateTimeUtil::getUserPreferredTimeZone());

    dirPersonName.FirstName     = conpeek(_c, #FirstName);
    dirPersonName.MiddleName    = conpeek(_c, #MiddleName);
    dirPersonName.LastName      = conpeek(_c, #LastName);
    newHcmWorker = HcmWorker::find(HcmWorkerTransition::newCreateHcmWorker(dirPersonName
                                                                           , conpeek(_c, #EmployeeNumber)
                                                                           , companyInfo.RecId
                                                                           , hcmEmploymentType
                                                                           , employmentStartDateTime
                                                                           , employmentEndDateTime));

    if (newHcmWorker.RecId == 0)
    {
        ret = false;
    }

    if (newHcmWorker.RecId == 0)
    {
        // Updating an existing worker

        // If there is no active employment for the worker
        newEmploymentRecId = HcmWorkerTransition::newCreateHcmEmployment(newHcmWorker.RecId, companyInfo.RecId,
                hcmEmploymentType, employmentStartDateTime, employmentEndDateTime);


        if (newEmploymentRecId == 0)
        {
            ret = false;
        }
    }

    if (ret)
    {
        if(numberSeqPersonnelNum)
        {
            // mark number sequence based ID consumed
            numberSeqPersonnelNum.used();
        }
    }
    else
    {
        if(numberSeqPersonnelNum)
        {
            numberSeqPersonnelNum.abort();
        }

        dirPerson.clear();
        dirPersonName.Person = 0;
    }

    hcmPersonPrivateDetails.initValue();
    hcmPersonPrivateDetails.Person      = dirPersonName.Person;
    hcmPersonPrivateDetails.BirthDate   = HrmImportEmployeeMasterdata::convDate(conpeek(_c, #BirthDate));
    hcmPersonPrivateDetails.Gender      = HrmImportEmployeeMasterdata::convGender(conpeek(_c, #Gender));
    hcmPersonPrivateDetails.insert();

    dirPerson                   = dirPerson::find(dirPersonName.Person, true);
    dirPerson.Initials          = conpeek(_c, #Initials);
    dirPerson.ProfessionalTitle = conpeek(_c, #Position);
    dirPerson.update();

    //Create address
    axLogisticsLocation = new AxLogisticsLocation();
    axLogisticsLocation.validateInput(true);
    axLogisticsLocation.parmIsPostalAddress(NoYes::Yes);
    axLogisticsLocation.parmDescription(HrmImportEmployeeMasterdata::createDescription(dirPersonName));
    axLogisticsLocation.save();

    axLogisticsPostalAddress    = new AxLogisticsPostalAddress();
    axLogisticsPostalAddress.parmLocation(axLogisticsLocation.parmRecId());
    axLogisticsPostalAddress.validateInput(true);
    axLogisticsPostalAddress.parmCountryRegionId(HrmImportEmployeeMasterdata::defaultCountryRegionId());
    axLogisticsPostalAddress.parmZipCode(conpeek(_c, #PostalCode));
    axLogisticsPostalAddress.parmZipCodeRecId(LogisticsAddressZipCode::find(conpeek(_c, #PostalCode)).RecId);
    axLogisticsPostalAddress.parmStreet(conpeek(_c, #Address));
    axLogisticsPostalAddress.parmCity(LogisticsAddressZipCode::find(conpeek(_c, #PostalCode)).City);
    axLogisticsPostalAddress.parmCityRecId(LogisticsAddressZipCode::find(conpeek(_c, #PostalCode)).CityRecId);
    axLogisticsPostalAddress.save();

    DirParty::addLocation(dirPersonName.Person, axLogisticsLocation.parmRecId(), true, true, true);
}


This method is used to update the employee

Update
private void employeeUpdate(container _c)
{
    boolean                                 ret = true;
    CompanyInfo                             companyInfo;
    ValidFromDateTime                       employmentStartDateTime;
    ValidToDateTime                         employmentEndDateTime;
    HcmWorker                               hcmWorker;
    DirPerson                               dirPerson;
    DirPersonName                           dirPersonName;
    HcmEmploymentType                       hcmEmploymentType = HcmEmploymentType::Employee;
    HcmPersonPrivateDetails                 HcmPersonPrivateDetails;
    AxLogisticsPostalAddress                axLogisticsPostalAddress = new AxLogisticsPostalAddress();
    AxLogisticsLocation                     axLogisticsLocation;
    Description                             description_Old;
    HcmEmployment                           hcmEmployment;
    LogisticsLocation                       logisticsLocation;
    LogisticsPostalAddress                  logisticsPostalAddress;
    DirPartyLocation                        dirPartyLocation;
    ;

    companyInfo = companyInfo::find();
    hcmWorker   = hcmWorker::findByPersonnelNumber(conpeek(_c, #EmployeeNumber));

    //Update dirPersonName
    dirPersonName   = dirPersonName::find(hcmWorker.Person, true);
    description_Old = HrmImportEmployeeMasterdata::createDescription(dirPersonName);
    if (   dirPersonName.FirstName  != conpeek(_c, #FirstName)
        || dirPersonName.MiddleName != conpeek(_c, #MiddleName)
        || dirPersonName.LastName   != conpeek(_c, #LastName))
    {
        dirPersonName.validTimeStateUpdateMode(ValidTimeStateUpdate::Correction);
        dirPersonName.FirstName     = conpeek(_c, #FirstName);
        dirPersonName.MiddleName    = conpeek(_c, #MiddleName);
        dirPersonName.LastName      = conpeek(_c, #LastName);
        dirPersonName.update();
    }

    //Update hiring
    employmentStartDateTime = datetobeginUtcDateTime(HrmImportEmployeeMasterdata::convDate(conpeek(_c, #DateOfHiring)), DateTimeUtil::getUserPreferredTimeZone());
    employmentEndDateTime   = DateTimeUtil::applyTimeZoneOffset(DateTimeUtil::maxValue(), DateTimeUtil::getUserPreferredTimeZone());

    hcmWorker       = HcmWorker::findByPersonnelNumber(conpeek(_c, #EmployeeNumber));
    hcmEmployment   = hcmEmployment::getActiveEmploymentsByWorker(hcmWorker.RecId, employmentStartDateTime, employmentEndDateTime, true);
    if (hcmEmployment.RecId)
    {
        HcmWorkerTransition::newUpdateHcmEmployment(hcmEmployment, employmentStartDateTime, employmentEndDateTime);
    }
    else
    {
        hcmWorker = HcmWorker::find(HcmWorkerTransition::newCreateHcmWorker(dirPersonName
                                                                           , conpeek(_c, #EmployeeNumber)
                                                                           , companyInfo.RecId
                                                                           , hcmEmploymentType
                                                                           , employmentStartDateTime
                                                                           , employmentEndDateTime));
    }

    hcmPersonPrivateDetails = HcmPersonPrivateDetails::findByPerson(hcmWorker.Person, true);
    if (hcmPersonPrivateDetails)
    {
        if (   hcmPersonPrivateDetails.BirthDate    != HrmImportEmployeeMasterdata::convDate(conpeek(_c, #BirthDate))
            || hcmPersonPrivateDetails.Gender       != HrmImportEmployeeMasterdata::convGender(conpeek(_c, #Gender)))
        {
            hcmPersonPrivateDetails.BirthDate   = HrmImportEmployeeMasterdata::convDate(conpeek(_c, #BirthDate));
            hcmPersonPrivateDetails.Gender      = HrmImportEmployeeMasterdata::convGender(conpeek(_c, #Gender));
            hcmPersonPrivateDetails.update();
        }
    }
    else
    {
        hcmPersonPrivateDetails.initValue();
        hcmPersonPrivateDetails.Person      = dirPersonName.Person;
        hcmPersonPrivateDetails.BirthDate   = HrmImportEmployeeMasterdata::convDate(conpeek(_c, #BirthDate));
        hcmPersonPrivateDetails.Gender      = HrmImportEmployeeMasterdata::convGender(conpeek(_c, #Gender));
        hcmPersonPrivateDetails.insert();
    }

    dirPerson                   = dirPerson::find(dirPersonName.Person, true);
    if (   dirPerson.Initials               != conpeek(_c, #Initials)
        || dirPerson.ProfessionalTitle      != conpeek(_c, #Position))
    {
        dirPerson.Initials          = conpeek(_c, #Initials);
        dirPerson.ProfessionalTitle = conpeek(_c, #Position);
        dirPerson.update();
    }

    //Update or Create address
    select firstOnly forUpdate logisticsLocation
        where logisticsLocation.Description == description_Old
        join dirPartyLocation
            where dirPartyLocation.Location == logisticsLocation.RecId
               && dirPartyLocation.Party    == dirPerson.RecId;

    if (logisticsLocation)
    {
        axLogisticsLocation = AxInternalBase::construct(logisticsLocation);
    }
    else
    {
        axLogisticsLocation = new AxLogisticsLocation();
    }

    axLogisticsLocation.validateInput(true);
    axLogisticsLocation.parmIsPostalAddress(NoYes::Yes);
    axLogisticsLocation.parmDescription(HrmImportEmployeeMasterdata::createDescription(dirPersonName));
    axLogisticsLocation.save();


    //Update or Create postaladdress
    select firstOnly forUpdate logisticsPostalAddress
        where logisticsPostalAddress.Location == axLogisticsLocation.parmRecId();

    if (logisticsPostalAddress)
    {
        axLogisticsPostalAddress = AxInternalBase::construct(logisticsPostalAddress);
    }
    else
    {
        axLogisticsPostalAddress = new AxLogisticsPostalAddress();
    }

    axLogisticsPostalAddress.parmLocation(axLogisticsLocation.parmRecId());
    axLogisticsPostalAddress.validateInput(true);
    axLogisticsPostalAddress.parmCountryRegionId(HrmImportEmployeeMasterdata::defaultCountryRegionId());
    axLogisticsPostalAddress.parmZipCode(conpeek(_c, #PostalCode));
    axLogisticsPostalAddress.parmZipCodeRecId(LogisticsAddressZipCode::find(conpeek(_c, #PostalCode)).RecId);
    axLogisticsPostalAddress.parmStreet(conpeek(_c, #Address));
    axLogisticsPostalAddress.parmCity(LogisticsAddressZipCode::find(conpeek(_c, #PostalCode)).City);
    axLogisticsPostalAddress.parmCityRecId(LogisticsAddressZipCode::find(conpeek(_c, #PostalCode)).CityRecId);
    axLogisticsPostalAddress.save();

    DirParty::addLocation(dirPersonName.Person, axLogisticsLocation.parmRecId(), true, true, true);
}

Read more...

AX for Retail 2012 R2: Installing the Real-time Service

AX for Retail 2012 R2: Installing the Real-time Service    

    

[Note:  Please see the companion article for Troubleshooting Tips for the Real-time Service.]
Possibly the biggest change with AX for Retail 2012 R2 is the re-architecting of the Retail Transaction Service.
The first thing you will notice is that the name has been changed: Retail Transaction Service is now Commerce Data Exchange: Real-time Service. Store Connect was also renamed to Commerce Data Exchange: Synch Service. While it may take some getting used to, these new names are much better descriptors of their actual functionality.
Along with the name change, Real-time Service has fundamentally changed from a Windows Service to an IIS Web Service. As mentioned in a previous article, the service itself really doesn't do a whole lot functionally: it acts as a traffic handler between the POS and the Headquarters to share real-time information. All actual logic is written in X++ code hosted in the AOS via the .Net Business Connector.  This part hasn’t changed.
This architecture change means that installation and configuration has changed quite a bit. This article will go through these steps to get you up and running with the new Real-time Service:

• Installing the Real-time Service
• Adding the SSL certificate to the Windows server
• Finding the certificate thumbprint and common name
• Creating the Real-time Service Web site in IIS
• Configuring the Real-time Service in Retail Headquarters
• Testing the Real-time Service from the POS

Installing the Real-time Service
The Real-time Service itself is still a component of the Microsoft Dynamics AX installer and can be found under Retail Components > Commerce Data Exchange > Real-time Service:


The Real-time Service needs to reside on a Windows server that has Internet Information Services (IIS) installed and configured. It also needs to communicate to an AOS, so the .Net Business Connector component also needs to be installed. You will notice that the Retail Salt Utility also gets installed with the Real-time Service.
Even though the Real-time Service is a relatively light-weight component, in a production environment it is good idea to install it on a non-AOS server.
One thing that may be a bit confusing is the fact that while the Real-time Service is now a Web service, it has nothing to do with the existing Web services on IIS component also found in the AX installer. Those Web services are used for other purposes, most notably allowing other applications to integrate with Dynamics AX. You do not need to install that component as part of the Real-time Service installation.
Upon successful installation you should get three folders under the Real-time Services folder (C:\Program Files (x86)\Microsoft Dynamics AX\60\Commerce Data Exchange\Real-time Services):

5.1 and 6.1 are there because AX for Retail 2012 R2 now has "N-1" support for previous versions of the POS. These versions of the Real-time Service are still implemented as a Windows Service and are configured just like Retail Transaction Service was configured in previous versions.

Since we are focusing on AX for Retail R2, we'll leave that topic for another article.
Adding the SSL certificate to the Windows server
Because the Real-time Service is now a Web service, an SSL certificate is required for communication between the POS and the Real-time Service. Here are three options for installing the certificate:
Requesting and Installing a certificate from IIS Management Console
For a production environment you will purchase and install an official certificate. This is the same thing you would do for implementing SSL on any externally-facing web site. Instructions can be found here: http://technet.microsoft.com/en-us/library/cc731977(v=ws.10).aspx
Using Powershell to install a certificate
If you already have received a certificate from your provider or are migrating one from a different server, you may have the file in a PFX format. If this is the case, you can use the provided Powershell script to install it:

• Open an elevated Powershell prompt:

• Navigate to the "Sample Deployment Scripts" folder in the Real-time Services directory and run the InstallServerCertificate.ps1 script.
• When prompted, enter the path to your PFX file and the private key password.
• If all is successful you will get a message that the certificate was successfully installed:

Creating a self-signed test certificate
If you want to get Real-time Service up and running in a test environment, you may wish to create your own self-signed test certificate. This is a good step-by-step walkthrough of how to do this: http://weblogs.asp.net/scottgu/archive/2007/04/06/tip-trick-enabling-ssl-on-iis7-using-self-signed-certificates.aspx
Finding the Certificate Thumbprint and Common Name
To verify that the certificate was installed correctly, we can navigate to it in the Internet Information Services (IIS) management console and grab its thumbprint. Open the IIS management console and select the local server in the navigation tree.  Double-click on Server Certificates to open the list of certificates that are installed on the server:

You should see your certificate in the list:


Double-click your certificate to open it.  navigate to the Details tab and then down to the Thumbprint property. Copy the 20-digit (40 characters) hex string to your clipboard - we will need it later.


Also, while on the Details tab, take note of the "Subject" property. This is the Common Name which will be used when creating the Real-time Service profile in Headquarters.
Creating the Real-time Service Web service
Creation of the Real-time Service itself is done with another Powershell script. In the same folder execute the InstallCommerceDataExchangeRealtimeService.ps1 script. The script will prompt for a number of parameters:

UserAccount: The user account to run the service as (domain\user). This is the account that will log in to Dynamics AX via the .Net Business Connector. This is the same user that you would have used for Windows service in previous versions of Retail Transaction Service.
Password: The password for the user account.
ServiceBinarySourceFolder: The service binary folder. This is the location of the DLLs that comprise the Real-time Service. By default this directory is C:\Program Files (x86)\Microsoft Dynamics AX\60\Commerce Data Exchange\Real-time Services\6.2\. These files will be copied to the Web site that is created. Tip: Do not add the 'bin' subfolder at the end of this string.

ServerCertificateThumbprint: The server certificate thumbprint noted above. You should remove the spaces from the 40-character string.

The script will do some pre-requisition checks and then if all goes well, it will create the site:

If something fails, you will need to perform an uninstall before attempting again. Run the UninstallCommerceDataExchangeRealtimeService.ps1 script to do this. This script takes only one parameter:

ServiceInstallFolder - This is the destination location that the source binary files were copied to. By default this is C:\inetpub\DynamicsAxRetail\CommerceDataExchangeRealtimeService.

Testing the Real-time Service Web service
If the Powershell script successfully installed the Web service, you can open IIS Management Console to validate. First, navigate to Application Pools…

… and then to Sites:

After confirming that they were successfully created, you can test the Web service via a Web browser.   Right-click on the CommerceDataExchangeRealtimeService application and select Switch to Content View:



You should see Service.svc in the list.  Right-click on it and select Browse:



If everything is working correctly, your Web browser should launch and you will see a screen like the following:

Edit:  The following step is not necessary.  If the Real-time Services resides on a non-AOS machine, it will use the AOS that the .Net Business Connector is configured to use.
If you are running the Real-time Service on a non-AOS machine (and hopefully you are!) then you need to perform one additional step before the Web service will work. By default, the service attempts to use the default AOS on the local machine. Pointing it to an AOS is similar to the steps in previous versions of the Retail Transaction Service.
 In a text editor, open the Web.config for the Web service. By default this is located at C:\inetpub\DynamicsAxRetail\CommerceDataExchangeRealtimeService.

Add the correct AOS information to the ObjectServer key:

<add key="ObjectServer" value="MicrosoftDynamicsAX@DAX2012:2712" />

Configuring the Real-time Service in Retail Headquarters
Now that we have confirmed the Real-time Service Web service is working correctly, we need to configure it in Headquarters and push it down to the POS.
In Dynamics AX navigate to Retail > Setup > Retail scheduler > Channel integration > Real-time Service profiles. Create a new profile with the following information:

Server: The name of the machine hosting the Web service. This must be a name that can be resolved to an IP address. Keep in mind that many POS machines will be connecting via the Internet, so it must be an externally-available server.
Port: The port of the Web service. By default, this value should be 808 for net.tcp binding. A firewall exception should be created to allow the POS machines to communicate via this port.
Protocol: While we tested the Web service using http binding, it is recommended that net.tcp binding be used here.
Web application name: This is the name of the web application that hosts Real-time Service. By default it is CommerceDataExchangeRealtimeService.
Common Name: This is used to identify the certificate that is being used for secure communications. It should match the "Subject" property of the certificate (see the "Finding the Thumbprint for the Certificate" section above).
Passphrase: This is the passphrase that the POS application will use to authenticate to the Real-time Service. Since this is encrypted and stored in a table that gets replicated to the POS database, you can enter any value here as long as it is non-blank.
Language: The language that will be used by the Real-time service.
Real-time Service version: If you will be using the Real-time Service with a previous version of AX for Retail POS (AX 2009 or AX 2012 Feature Pack) select the version from the drop-down.

As in previous versions, the Real-time Service profile is assigned to a specific register. Navigate to Retail > Setup > POS > POS registers and open a register. The profile you created should be assigned under General > Profiles:

After assigning the Real-time Service profile to a register, the changes can be pushed to the POS database by running the N-1090 job.
Testing the Real-time Service from the POS
The easiest way to test that the Real-time Service is working correctly is to perform an Inventory Lookup from the POS. Launch the POS and navigate to the Inventory Lookup button (in the sample layout this is under Cashier Tasks). In the Inventory Lookup form, enter a valid Item ID and press enter. If the POS is able to read information from Headquarters via the Real-time Service, you will see the item information fill in:

Wrap-up
You can tell by the number screenshots alone that installing the Real-time Service is more complicated in AX for Retail 2012 R2. There are also lots of opportunities for things to not work correctly the first time around. I will address some of the more common ones in my next article. In the meantime, if you run into difficulties, please create a support incident and we can help get you past any obstacles.
Edits:

• December 27, 2012:  Easier steps for viewing server certificates and browsing to the Web Service.  Removed section on configuring service to point to a different AOS.

Read more...

Install multiple Enterprise Portals on the same server [AX 2012]

4 out of 5 rated this helpful - Rate this topic

Updated: February 1, 2013
Applies To: Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

This topic describes how to install and configure multiple Enterprise Portals on the same server. Portals can be configured to access the same or different Microsoft Dynamics AX Application Object Server (AOS) instances, as described in this topic.

Caution

Before you continue, consider the following. If you install multiple portals on the same server, you create a single point of failure for all portals if SharePoint or IIS are not available on the server. Scheduled downtime for maintenance affects all portals on the server which might limit how often you can perform maintenance. If you plan to install portals for development, testing, and production on the same server (not recommended) you could unintentionally deploy development changes to production which could cause data-integrity problems. Multiple portals consume more resources on the server than a single portal. Plan your topology accordingly. You can deploy multiple portals on the same server as long as the user controls are the same. This means the controls must use the same AX model. Multiple portals on the same server are not supported if the codebase is different.

Enterprise Portal and the AOS

---

Enterprise Portal determines which AOS instance to connect to by reading a Microsoft Dynamics AX client configuration. If you install Enterprise Portal on a server that hosts an AOS instance, the client configuration is stored, by default, in the registry on the AOS. If you install Enterprise Portal on a server that does not host an AOS or if Setup cannot locate a client configuration on the Web server, you are prompted to specify the location of the client configuration. If you create additional Enterprise Portals on the server, those portals use the AOS that is specified in the client configuration unless you specify a different client configuration, as described in this topic.

Multiple portals on the same server that use the same AOS

---

By default, when you install Enterprise Portal, Setup creates an Enterprise Portal site on the SharePoint-80 Web application. You can create additional sites on the port 80 Web application by using SharePoint Central Administration. All sites created in this manner use the same AOS. For more information about how to create an Enterprise Portal site, see Create an Enterprise Portal site.
If you create additional web applications by using SharePoint Central Administration, you must deploy Enterprise Portal on the new web applications by using Microsoft Dynamics AX Setup. You can then create additional sites on the new web application by using SharePoint Central Administration. All sites created in this manner use the same AOS.

Multiple portals on the same server that use different AOSs

---

To install multiple portals on the same server and have those portals connect to different AOS instances, you must follow these steps.

Before you begin

Enterprise Portal determines which AOS to connect to by reading a Microsoft Dynamics AX client configuration. To install multiple portals on the same server and have those portals connect to different AOS instances, the portals must read separate Microsoft Dynamics AX client configurations. Create one or more Microsoft Dynamics AX client configuration files by using the Microsoft Dynamics AX 2012 Configuration utility and store the configuration files on a network share. For more information about how to create a configuration file, see Manage a client configuration.

1. Use Microsoft Dynamics AX Setup to install Enterprise Portal on the server. By default, Setup creates an Enterprise Portal intranet site on the SharePoint-80 Web application. For the purpose of this procedure, this portal is called Portal1 and it is connected to AOS1. For more information about how to install Enterprise Portal, see Install Enterprise Portal on a single server.
   
2. Create a new web application on the Enterprise Portal server by using SharePoint Central Administration. For more information about how to create a new web application, see the Microsoft SharePoint 2010 products online Help.
   
3. Install Enterprise Portal on the new web application by using Microsoft Dynamics AX Setup. By default, a second portal is created on the port that is specified in SharePoint Central Administration. For the purpose of this procedure, this portal is called Portal2. Copy the URL of Portal2. You will need the URL later in this procedure when you register the portal. Portal2 is currently connected to AOS1.
   
4. Specify the new Microsoft Dynamics AX client configuration file for Portal2 by editing the web.config file. By default the web.config file is located in the following directory: C:\inetpub\wwwroot\wss\VirtualDirectories\<port number>
   
5. Add the following Microsoft.Dynamics element under </system.web>. Replace <server_name>, <path>, and <configuration_file>.axc with the information specific to your computing environment. For example: <Session Configuration="C:\inetpub\wwwroot\dynamicsax.axc" />
   <Microsoft.Dynamics>
   <Session Configuration="\\<server_name>\<path>\<configuration_file>.axc" />
   </Microsoft.Dynamics>
   
6. Save your changes in the web.config file.
   
7. Verify that the Business Connector Proxy account for AOS2 is the same as AOS1. Click System administration > Setup > System > System service accounts.
   
8. Use the Microsoft Dynamics AX client to register Portal2 on AOS2. Click System administration > Setup > Enterprise Portal > Web sites. Enter the URL in the Internal URL and External URL fields.
   
9. In the Type field, click Full (Web parts and site templates). Portal2 is now connected to AOS2.
   
10. Delete Portal2 from the Web sites form on AOS1.
    
11. On the Enterprise Portal server, open a command prompt and run the following command. This command closes stale Business Connector connections: iisreset /noforce
    

Read more...

Enterprise Portal Architecture

The following diagram provides a high-level overview of the Enterprise Portal architecture.

Read more...

Install Enterprise Portal

This section describes how to install Enterprise Portal by using Setup. If you are installing other Microsoft Dynamics AX components at the same time, the installation pages vary, based on the components that you are installing.

Tip

By default, when you install SharePoint, the system creates a Web application on port 80. Microsoft Dynamics AX Setup deploys an Enterprise Portal site on the port 80 Web application unless you specify a different Web application. If you do not intend to deploy Enterprise Portal on the default port-80 Web application, you must use SharePoint Central Administration to create a new Web application before you install Enterprise Portal. Also note, if you intend to deploy Enterprise Portal on a Web application that is already configured to use a host header, you must use SharePoint Central Administration to create a new Web application using the host header before you install Enterprise Portal. For any new Web application, you must specify the Business Connector proxy account as the application pool account in the Configurable list.

1. Start Microsoft Dynamics AX Setup. Under Install, select Microsoft Dynamics AX components.
   
2. Advance through the first wizard pages.
   
3. If the Setup Support files have not yet been installed on the computer, the Select a file location page is displayed. The Setup Support files are required for installation. Enter a file location or accept the default location, and then click Next. On the Ready to install page, click Install.
   
4. On the Select installation type page, click Custom installation, and then click Next.
   
5. On the Select components page, select Enterprise Portal (EP), and then click Next.
   
6. On the Prerequisite validation results page, resolve any errors. For more information about how to resolve prerequisite errors, see Check prerequisites. When no errors remain, click Next.
   
7. On the Select a file location page, select the location where you want to install 32-bit versions of Microsoft Dynamics AX files, and then click Next.
   
8. On the Specify a location for configuration settings page, specify whether you want Enterprise Portal to access configuration information from the registry on the local computer or from a shared configuration file. If you select to use a shared configuration file, you must enter the network location of the file. Click Next.
   
9. On the Connect to an AOS instance page, enter the name of the computer that is running the Application Object Server (AOS) instance that you want to connect to. You can optionally specify the name of the AOS instance, the TCP/IP port number, and the WSDL port for services. Click Next.
   

   Note
   If you entered AOS connection information for other Microsoft Dynamics AX components that are installed on this computer, this screen is not displayed. Subsequent installations on this computer reuse the existing AOS connection.

10. On the Specify Business Connector proxy account information page, enter the password for the proxy account that is used by the .NET Business Connector. Click Next.
    
11. On the Configure a Web site for Enterprise Portal page, select a web site. If no web sites are available in the list, you must cancel Setup, create a web site by using SharePoint Central Administration, and then try the installation again.
    We recommend that you select the Configure for Windows SharePoint Services option. If you select this option, Setup verifies that the site is a SharePoint site. If the site is not a SharePoint site, Setup extends the site in SharePoint. Setup also sets the application pool to run under the service account and sets the authentication method to Windows NTLM.
    

    Important

    Note the following important information about the Create Web site option: Clear this option if you are installing Enterprise Portal for a public site, such as an unsolicited vendor portal. For public sites, you must create the Enterprise Portal site by using the public site template. For more information, see Create a public Enterprise Portal site. If you are installing Enterprise Portal for a stand-alone installation select the Create Web site option to create a site at the following URL: http://ServerName/sites/DynamicsAX. Setup creates a new site that uses port 80.

    Click Next.
    

    Note
    If your business or organization purchased a developer license for Microsoft Dynamics AX, you can change the URL for the web site, title, and description before you complete the installation. Modify the EPSetupParams file in the Application Object Tree (AOT) (Web > Web Files > Static Files > EPSetupParams).

12. On the Prerequisite validation results page, resolve any errors. When no errors remain, click Next.
    
13. On the Ready to install page, click Install.
    
14. After the installation is complete, click Finish to close the wizard.
    

Read more...

Create a public Enterprise Portal site [AX 2012]

                       

This topic describes how to create a public Enterprise Portal website. By using a public site, potential customers and vendors can register with the business or organization.

Create a new Web application in SharePoint Central Administration

---

By default, when you install the Enterprise Portal framework by using Setup, the system creates a Web application and a web site that use Integrated Windows authentication. You cannot use the default Web application and web site for an Enterprise Portal public site, because a public site requires anonymous authentication. The following procedure describes how to use SharePoint Central Administration to create a new Web application.

1. Open SharePoint Central Administration (Start > Programs > Microsoft SharePoint Products > SharePoint Central Administration).
   
2. Create a new Web application (Application Management > Manage Web applications > New).
   
3. In the Authentication section, verify that Classic Mode Authentication is selected.
   
4. In the IIS Web Site section, click Create a new IIS Web site. You can adjust the Port, Host Header, and Path settings, as necessary, or you can leave the default settings.
   
5. In the Security Configuration section, leave the default settings. You will configure authentication later in this topic.
   
6. In the Public URL section, enter the information that you want.
   
7. In the Application Pool section, click Create a new application pool, and then click Configurable. In the drop-down menu, select the name of the Business Connector proxy account. You can view the name of the Business Connector proxy account in the Microsoft Dynamics AX client on the Administration module, under Setup > Security > System Service accounts.
   
8. Enter information in the remaining sections, and then click OK. SharePoint creates the new Web application.
   

Deploy Enterprise Portal on the new Web application

---

Use Microsoft Dynamics AX Setup to deploy Enterprise Portal binaries to the new Web application. If you previously installed Enterprise Portal on the server, you still need to run Setup to deploy binaries and files to the new web application. For more information, see Install Enterprise Portal on a single server. You must clear the Create Web site option in Setup. You will create the site later in this topic.

Create a site collection that uses the public template

---

Enterprise Portal includes separate templates for internal sites and public sites. Use this procedure to create a new site collection that uses the public template.

1. In SharePoint Central Administration under Application Management, click Create site collections.
   
2. In the Web Application section, select the Web applications that you created earlier in this document.
   
3. Enter a title and description.
   
   

   Important
   You must enter a unique title and description for each Enterprise Portal site. If you create a new web site by using SharePoint Services or IIS Manager, and a title or site description matches an existing site, Enterprise Portal will not deploy on the new site.

4. Specify a URL.
   
5. In the Template Selection section, click Custom, and then click Microsoft Dynamics Public.
   
6. Specify collection administrators and quota details.
   
7. Click OK.
   
8. After the new SharePoint site collection is created, open a command prompt, type iisreset /noforce, and then press ENTER.
   

Configure anonymous authentication in IIS

---

You must configure the web site to use anonymous authentication in IIS.

1. Open IIS manager (Start > Administrative Tools > Internet Information Services (IIS) Manager).
   
2. Expand the local computer, expand the Sites directory, and then click the Web application that you created earlier in this topic.
   
3. In the center pane under IIS, double-click Authentication.
   
4. Click Anonymous Authentication, and then click Enable. Disable all other types of authentication.
   

Configure anonymous authentication in SharePoint

---

You must configure the web site to use anonymous authentication in SharePoint.

1. In SharePoint Central Administration under Application Management, click Manage Web applications.
   
2. In the Web Application section, select the Web applications that you created earlier.
   
3. Click Authentication Providers.
   
4. Under Zone, click Default.
   
5. Under Anonymous Authentication, click Enable anonymous access.
   
6. Click OK.
   

Prevent company navigation from displaying in the public site

---

By default, any new Enterprise Portal site includes a drop-down list that enables users to navigate among different companies if they have the appropriate permissions. Although guest users have no permissions to navigate companies, and the public site displays no company-specific information, we recommend that you disable the company navigation. This way, guest users cannot see the naming that is associated with your different companies.

1. Click System administration > Setup > Enterprise Portal > Web sites.
   
2. Select the site that you created earlier, and then click the General tab.
   
3. Clear the Company independent option.
   
4. Click Close.
   
5. Open a command prompt, type iisreset /noforce, and then press ENTER.
   

Next steps

---

After you create the site, complete the steps in the following table to finish deploying the site.

Task	For more information…
Configure Enterprise Portal to use Secure Sockets Layer (SSL) encryption. Microsoft recommends that you encrypt data by using SSL for all external-facing Enterprise Portal sites. SSL is optional for internal-use-only employee portals.	Configure Enterprise Portal to use Secure Sockets Layer
Configure the Microsoft Dynamics AX guest-user account and corresponding security roles.	Enable users to access Enterprise Portal
Register the site IP address and a URL with a domain name service, so that users can find the site on the Internet.	Contact a domain provider

View the site as an anonymous user

---

After you have enabled the guest-user account in Microsoft Dynamics AX and assigned the account to the appropriate roles, as described in Enable users to access Enterprise Portal, you can view the site as an anonymous user. To do this, enable anonymous-logon user authentication in a Web browser. The following procedure describes how to enable anonymous-logon user authentication for Internet Explorer. If you are using a Web browser other than Internet Explorer, see that product's documentation for information about how to enable anonymous-logon user authentication.

1. Open Internet Explorer.
   
2. Click Tools > Internet Options > Security > Internet or Local intranet > Custom level.
   
3. Under User Authentication, select Anonymous logon, and then click OK.
   
4. Open the site in a Web browser.  

Read more...