Implementing Rockton’s SmartFill: Customising Search Options

Rockton SoftwareThis post is part of a series of posts on Implementing Rockton’s SmartFill.

While SmartFill can be used out of the box with the search being configured to lookup on several fields, it is possible to customise the search options so that more fields can be searched against.

If we take the Vendor search as an example, it uses the following fields for the sdearch:

  • Vendor ID
  • Vendor Name
  • Vendor Class

To change the search configuration, select SmartFill Objects (Administration area page » Setup » SmartFill » SmartFill Objects). Scroll down and locate the Vendors in the list; select it and click OK:

SmartFill Objects

Continue reading “Implementing Rockton’s SmartFill: Customising Search Options”

Implementing Rockton’s SmartFill: Registration

Rockton SoftwareThis post is part of a series of posts on Implementing Rockton’s SmartFill.

While SmartFill will work without a licence in the Fabrikam sample company, to use it in any other company, you need to register the module. Your partner can purchase the keys for you; once the order is compelte, the registration can be updated in Microsoft Dynamics GP.

To do this, open the Rockton Software Registration Issues (Microsoft Dynamics GP menu » Tools » Setup » SmartFill » Registration) window. Ensure SmartFill is marked in the Product Name column and click the Get Keys button:

Rockton Software Registration Issues

Once the keys have been retrived, the Message column will show Registered. Click to see details. SmartFill is now available to use in all companies.

Click to show/hide the Implementing Rockton's SmartFill Series Index

Implementing Rockton’s SmartFill: Client Installation

Rockton SoftwareThis post is part of a series of posts on Implementing Rockton’s SmartFill.

The second step in implementing SmartFill is to install the remaining clients.

Using the previously downloaded installer, extract the downloaded file and run the SmartFillSetup.exe as Administrator by right-clicking:

SmartFillSetup.exe

Continue reading “Implementing Rockton’s SmartFill: Client Installation”

Implementing Rockton’s SmartFill: What Is SmartFill

Rockton SoftwareThis post is part of a series of posts on Implementing Rockton’s SmartFill.

Before starting the installation, I thought it might be useful to do a post, covering what functionality SmartFill contains.

Simply put, SmartFill allows you to perform a more flexible lookup than the standard ones in Microsoft Dynamics GP. For example, you can type only a few characters of an Item Number or Item Description and a list of data matching will be returned; the search performed is a begins with or contains (depending on configuration) which makes it easy to find the required data.

By default SmartFill ships with a large number of default searches, but can be customised to add more or change the default ones; and can also be configured to to be available to 3rd party modules.

Click to show/hide the Implementing Rockton's SmartFill Series Index

Implementing Rockton’s SmartFill: Series Index

Rockton SoftwareI periodically take a look at different offering from ISVs, of which there are many. One that I’ve looked at recently is SmartFill from Rockton Software.

I figured a small series on implementing it might be useful as I step through the process myself. Over the new few posts, I’ll be installing and configuring SmartFill.

Implementing Rockton's SmartFill
Implementing Rockton's SmartFill: What Is SmartFill
Implementing Rockton's SmartFill: First Client Installation
Implementing Rockton's SmartFill: Client Installation
Implementing Rockton's SmartFill: Registration
Implementing Rockton's SmartFill: Search Using SmartFill
Implementing Rockton's SmartFill: Configuring Security
Implementing Rockton's SmartFill: Customising Search Options
Implementing Rockton's SmartFill: Review

Enabling Secure Connection for Web Services: Configure Workflow Setup

Microsoft Dynamics GPThis post is part of the Enabling Secure Connection for Web Services series.

With Web Services now configured for secure connections, the final step in the configuration is to amend the Workflow setup. This is done via the Workflow Setup window (Administration area page » Setup » System » Workflow Setup); despite this being on the System part of the menu, it is actually a Company window so any changes made will need to be repeated in all companies using Workflow.

There are two settings which need to be changed; both of them in the ,em>Enable E-Mail Actions section.

Change the Server Name to the externally accessible DNS hostname, change the Port to the relevant port and mark the This server requires a secure connection (SSL):

Workflow Setup

Continue reading “Enabling Secure Connection for Web Services: Configure Workflow Setup”

Enabling Secure Connection for Web Services: Final Service Configuration

Microsoft Dynamics GPThis post is part of the Enabling Secure Connection for Web Services series.

Over the last few posts, I’ve stepped through the changes to the Web Service configuration files. With all of these changes made, there are a small number of steps to now complte, or confirm as complete.

Firstly, as the configuration files have been changed, the Microsoft Dynamics GP Service Host needs to be restarted. This can be done via the Services control panel applet.

Secondly, ensure the firewall port for the secure port is configured to allow access.

Thirdly, I’d recommend verifying the Web Services are working correctly; when you test the services, use the updated paths for https access:

  • https://server.msdynamicsgp.co.uk:48666/DynamicsGPWebServices
  • https://server.msdynamicsgp.co.uk:48666/Dynamics/GPService

Click to show/hide the Enabling Secure Connection for Web Services Series Index

Enabling Secure Connection for Web Services: Update GP Workflow Service

Microsoft Dynamics GPThis post is part of the Enabling Secure Connection for Web Services series.

There are several configuration files which need to be amended to enable a secure connection for Web Services. The first is a href=’There are several configuration files which need to be amended to enable a secure connection for Web Services. The first is WSBindings.config, the second is the legacy endpoint config file, DynamicsGPLegacy.config, the second is the legacy endpoint config file, DynamicsGP.config and the fourth, being covered in this post, is the GP Workflow Service configuration file, GPWorfklowService.config, which is, by default, located in C:\Program Files\Microsoft Dynamics\GPWebServices\ServiceConfigs.

There are two elements which need to be updated in the services node:

  1. Change the bindingConfiguration node from WebHttpBindingTarget to WebHttpBindingTargetSSL.
  2. Add a new https baseAddress line using the new port and the externally accessible DNS hostname:
    <add baseAddress="https://SERVER.msdynamicsgp.co.uk:48666/Dynamics/GPService/rest"/>
      <service name="Microsoft.Dynamics.GP.WebServices.WorkflowActionRenderingEngineContract.WorkflowActionRenderingEngine">
        <endpoint behaviorConfiguration="GPWorkflowService.RestBehavior" binding="webHttpBinding" bindingConfiguration="WebHttpBindingTargetSSL" contract="Microsoft.Dynamics.GP.WebServices.WorkflowActionRenderingEngineContract.IWorkflowActionRenderingEngine"/>
        <endpoint name="aad" address="aad" behaviorConfiguration="GPWorkflowService.AzureRestBehavior" binding="webHttpBinding" contract="Microsoft.Dynamics.GP.WebServices.WorkflowActionRenderingEngineContract.IWorkflowActionRenderingEngine" bindingConfiguration="WebHttpBindingNoSecurity"/>
        <host>
          <baseAddresses>
            <add baseAddress="http://SERVER:48620/Dynamics/GPService/rest"/>
            <add baseAddress="https://SERVER.msdynamicsgp.co.uk:48666/Dynamics/GPService/rest"/>
          </baseAddresses>
        </host>
      </service>

Continue reading “Enabling Secure Connection for Web Services: Update GP Workflow Service”

Enabling Secure Connection for Web Services: Update Native Endpoint

Microsoft Dynamics GPThis post is part of the Enabling Secure Connection for Web Services series.

There are several configuration files which need to be amended to enable a secure connection for Web Services. The first is a href=’There are several configuration files which need to be amended to enable a secure connection for Web Services. The first is WSBindings.config; the second is the legacy endpoint config file, DynamicsGPLegacy.config and the third, being covered in this post, is the native endpoint configuration file, DynamicsGP.config, which is, by default, located in C:\Program Files\Microsoft Dynamics\GPWebServices\ServiceConfigs.

There are three elements which need to be updated in the services node:

  1. Change the behaviorConfiguration node from GPLegacyStaticMetadataBehavior to GPDynamicMetadataBehavior.
  2. Change the bindingConfiguration node from WSHttpBindingTarget to WSHttpBindingTargetSSL.
  3. Add a new https baseAddress line using the new port and the externally accessible DNS hostname:
    <add baseAddress="https://SERVER.msdynamicsgp.co.uk:48666/Dynamics/GPService"/>
<service name="Microsoft.Dynamics.GP.WebServices.Contract.DynamicsGP" behaviorConfiguration="GPDynamicMetadataBehavior">
        <endpoint address="Mex" name="http" binding="customBinding" bindingConfiguration="CustomBinding" contract="IMetadataExchange"/>
        <endpoint address="GPService" name="GPWebService" binding="wsHttpBinding" bindingConfiguration="WSHttpBindingTargetSSL" contract="Microsoft.Dynamics.GP.WebServices.Contract.IGPServices"/>
        <host>
          <baseAddresses>
            <add baseAddress="http://SERVER:48620/Dynamics/GPService"/>
            <add baseAddress="https://SERVER.msdynamicsgp.co.uk:48666/Dynamics/GPService"/>
          </baseAddresses>
        </host>
      </service>

Continue reading “Enabling Secure Connection for Web Services: Update Native Endpoint”

Enabling Secure Connection for Web Services: Update Legacy Endpoint

Microsoft Dynamics GPThis post is part of the Enabling Secure Connection for Web Services series.

There are several configuration files which need to be amended to enable a secure connection for Web Services. The first is a href=’There are several configuration files which need to be amended to enable a secure connection for Web Services. The first is WSBindings.config; the second is the legacy endpoint config file, DynamicsGPLegacy.config which is, by default, located in C:\Program Files\Microsoft Dynamics\GPWebServices\ServiceConfigs.

There are three elements which need to be updated in the services node:

  1. Change the behaviorConfiguration node from GPLegacyStaticMetadataBehavior to GPDynamicMetadataBehavior.
  2. Change the bindingConfiguration node from BasicHttpBindingTarget to BasicHttpBindingTargetSSL.
  3. Add a new https baseAddress line using the new port and the externally accessible DNS hostname:
    <add baseAddress="https://SERVER.msdynamicsgp.co.uk:48666/DynamicsGPWebServices"/>
   <services>
      <service name="Microsoft.Dynamics.GP.WebServices.LegacyContract.DynamicsGP" behaviorConfiguration="GPDynamicMetadataBehavior">
        <endpoint address="Mex" name="http" binding="customBinding" bindingConfiguration="CustomBinding" contract="IMetadataExchange"/>
        <endpoint address="DynamicsGPService.asmx" name="LegacyDynamicsGP" binding="basicHttpBinding" bindingConfiguration="BasicHttpBindingTargetSSL" contract="Microsoft.Dynamics.GP.WebServices.LegacyContract.IGPServicesLegacy"/>
        <host>
          <baseAddresses>
            <add baseAddress="http://SERVER:48620/DynamicsGPWebServices"/>
            <add baseAddress="https://SERVER.msdynamicsgp.co.uk:48666/DynamicsGPWebServices"/>
          </baseAddresses>
        </host>
      </service>
    </services>

Continue reading “Enabling Secure Connection for Web Services: Update Legacy Endpoint”