Setting up Currency ISO Code in Microsoft Dynamics GP

The Dynamics GP web service uses ISO codes to identify currencies in Microsoft
Dynamics GP.
Note: Web Services for Microsoft Dynamics GP does not support using the same ISO code for more than one currency.
To add ISO codes, complete the following procedure:
 1.  Open the Currency Setup window in Microsoft Dynamics GP.
          Choose Microsoft Dynamics GP menu >> Tools >> Setup >> System >>
          Currency and enter the system password to display this window.

 2. Display each currency.
            Use the Currencies lookup to display each currency.
            Press (Ctrl + L) or click the search icon to display the below window.

3. Select the Currency to set the ISO code
        For e.g. select US Dollars, the Following window appears.
4. Enter the ISO value and save the currency.
Enter the code in the ISO Code Text Field.
The following table lists the ISO values for the currencies commonly defined in
Microsoft Dynamics GP:
ISO Code
United States
European Union
New Zealand
 5. Save and Exit.
After entering the ISO code save the Currency and close the window.

Now the Currency set up is finished and able to access through GP web services.


Consume Any Web Service Using Eclipse + Axis

  1. Start Eclipse and create a new workspace named wsTest (click File -> Switch Workspace -> Other…)

  2. Create a new Java Project named wsTest (click File -> New -> Java Project)

  3. Create a new Web Service Client Proxy (click File -> New -> Other -> Web Services -> Web Service Client). In this case we are consuming a free, public web service that returns weather information for the United States. The URL for the WSDL definition is

  4. Create a new Java Class named (click File -> New -> Class)

  5. Copy and paste the following code into (overwrite the existing code): – double click to select all
    public class Test
     public static void main(String[] arg)
       WeatherSoapStub service = (WeatherSoapStub)new WeatherLocator().getWeatherSoap(new URL(""));
       WeatherReturn weather = service.getCityWeatherByZIP("47710");
       System.out.println("Location: " + weather.getCity() + ", " + weather.getState());
       System.out.println("Description: " + weather.getDescription());
       System.out.println("Temperature: " + weather.getTemperature() + " degrees");
      catch (Exception e)

    Note that we set the endpoint URL on line 10. The endpoint URL is typically the same as the WSDL definition URL except the endpoint URL does not include the ?WSDL query string parameter.

  6. Execute the code (click Run -> Run)

    You should see something resembling the following output:

    Location: Evansville, IN
    Description: Sunny
    Temperature: 49 degrees

Setting up a Subversion plug-in for Visual Studio 2008/2010

For Microsoft Visual Studio 2005, 2008, 2010 and 11 beta

Installation (2.1+)

 AnkhSVN 2.3.11269

  • Download AnkhSVN from  above download link. 
  • AnkhSVN is a free Subversion Client.
  • Run the AnkhSVN installer package (It automatically updates any previous versions).

Start using AnkhSVN from Visual Studio
Using an existing solution with AnkhSVN 2.1
  • Open your solution
  • If you are the first AnkhSVN 2.1 user of this solution
    • If glyphs do not appear automatically choose Tools -> Options -> Source Control and make sure AnkhSVN is the active source control provider.
  • Verify if the solution is connected to AnkhSVN
    • Right click the solution file. If you have an option that says ‘Add to Subversion’, your Solution is not connected yet
    • Click Add to Subversion and confirm adding the binding
    • If your project is not in an existing workingcopy you are now asked where to store your project
  • If some of the projects do not show glyphs
    • Check if the projects are connected in File -> Subversion -> Change Source Control
    • Make sure that at least the Solution and the projects missing glyphs are connected
      (Many project types do not require explicit binding)

Check out a Solution from Subversion
Using Open from Subversion
  • Select File -> Open -> Subversion Project
  • Choose a Url from the dropdown or click the globe icon to add a url
  • Browse to the solution of your choice
  • Click OK
  • In the next dialog select a local folder to store the project
  • Click OK and the solution will open automatically
Via the Repository Explorer 
  • Select View -> Repository Explorer.
  • When the tool window appears, choose the Plus-Folder icon to add your repository path and click OK.
  • Browse to the solution you would like to check out, right-click and choose Checkout Folder.
  • Browse to the location where you keep your working copy and press OK (you may need to create a directory first).
  • Open the solution inside Visual Studio. You will be asked whether to enable AnkhSVN for this solution, choose Yes.

Setting up a Subversion server in Windows using VisualSVN

Subversion is one of the widely used version controlling system amongst java developer community. Because of the flexibility and features that the Subversion provides, most of the developers have migrated to Subversion from CVS, which is another version controlling tool. If you want to setup a source controlling for your Java projects, you could install the Subversion core server and can create/manage data repositories directly from the command line. But if you want a Subversion product that just works out of the box, you need to have a look at the VisualSVN server.

VisualSVN Server – Subversion Server for Windows

VisualSVN is a free software that helps us to install and manage a Subversion server in Windows operating system. VisualSVN server comes with the core Subversion system, an Apache Server for running the Subversion server as Windows service and a visual management console. It also provides the access control for the subversion repositories, by creating users and groups.

Steps to setup a Subversion repository using VisualSVN server

  1. Download VisualSVN server and install it on your windows machine. When you install VisualSvn server, it also install the Windows service.
  2. Start the VisualSVN server Manager, which will open the repository browser.
VisualSVN - Subversion server for Windows

  1. To create a new repository for your project, right click on the Repositories and select ‘Create New Repository‘. This will ask you for the repository name. And, by default VisualSvn server will also creates the default folder structure (trunk,tag,branch) for your project.
    VisualSVN - Subversion server for Windows
  2. Once the repository is created, next step would be creating users and groups. To do this, right click on ‘Users’ and select ‘Create User’. Enter the user and and give password. Similar to this, you can create a group also and associate your user to the group.
    User creation: VisualSVN - Subversion server for Windows
  3. To give access to the repository for the newly created user, right click on the repository, select ‘Security’ and then from the ‘Properties’ window, click ‘Add’ to add users to our repository. Either a group or a user can be selected and added to the repository.
    VisualSVN - Subversion server for Windows
  4. After adding the user/group to the repository, the ‘access levels’ can be controlled from the ‘Properties’ window, as shown below.
    VisualSVN - Subversion server for Windows
  5. We are almost done. Now right click on your repository and select ‘Copy URL to Clipboard’ and share it with your fellow developers. This is your Subversion URL which can be accessed by other developers for checking out/checking in their code.

How to change XAMPP server port?

To change the XAMPP server port number:

  1. Stop the XAMPP server, if it is running already.
  2. Open the file [XAMPP Installation Folder]/apache/conf/httpd.conf.
  3. Now search for the string Listen 80 (I’m assuming that your XAMPP was using the port 80. Otherwise, just search for the string “Listen”). This is the port number which XAMPP uses. Change this 80 to any other number which you prefer.
  4. Then search for the string “ServerName” and update the port number there also.
  5. Now save and re-start XAMPP server and you are done.

Why do we need to change the port number? Because, these days, it is very common that a web developer needs to have multiple web servers running, all at the same time. For example, an XAMPP server can be used to run the local WordPress blog, while a JBoss server also needs to be up for testing a java web applications. In such scenarios, if two or more servers are trying to use the same port number, then the late comer will fail to get the port. So, it becomes necessary to change any one server’s port number to avoid the conflict.