A dark Mode for Outlook.com is now available.
To enable the theme, hit the Settings cog in the top right corner and then move the Dark mode slider to the right:
A dark Mode for Outlook.com is now available.
To enable the theme, hit the Settings cog in the top right corner and then move the Dark mode slider to the right:
This 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:
WebHttpBindingTarget
to WebHttpBindingTargetSSL
.<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”
This 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:
GPWCFStaticMetadataBehavior
to GPDynamicMetadataBehavior
.WSHttpBindingTarget
to WSHttpBindingTargetSSL
.<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”
This 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:
GPLegacyStaticMetadataBehavior
to GPDynamicMetadataBehavior
.BasicHttpBindingTarget
to BasicHttpBindingTargetSSL
.<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”
This 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 WSBindings.config which is, by default, located in C:\Program Files\Microsoft Dynamics\GPWebServices\ServiceConfigs.
There are three sections of this config file which need to be amended, but before making any changes, take a backup of the entire file.
The first section is the basicHttpBinding section. Replicate the BasicHttpBindingTarget binding:
SSL
Transport
<basicHttpBinding>
<binding name="BasicHttpBindingTarget" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true">
<readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"/>
<security mode="TransportCredentialOnly">
<transport clientCredentialType="Ntlm"/>
</security>
</binding>
<binding name="BasicHttpBindingTargetSSL" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true">
<readerQuotas maxDepth="2147483647" maxStringContentLength="2147483647" maxArrayLength="2147483647" maxBytesPerRead="2147483647" maxNameTableCharCount="2147483647"/>
<security mode="Transport">
<transport clientCredentialType="Ntlm"/>
</security>
</binding>
</basicHttpBinding>
Continue reading “Enabling Secure Connection for Web Services: Update Bindings”
This post is part of the Enabling Secure Connection for Web Services series.
The first step in enabling a secure connection for web services, is to bind the certificate to the port which will be used for secure access. As mentioned in the last post, I am using port 48666.
There are two commands which need to be run to bind the certificate; these need to be run via an elevated command prompt.
The first command registers the certificate for the new port; there are three parameters (highlighted) which need to be changed in the command:
Continue reading “Enabling Secure Connection for Web Services: Update Certificate Binding”
This post is part of the Enabling Secure Connection for Web Services series.
Before we start making any configuration changes to the Web Services for Microsoft Dynamics GP, there is a couple of decisions to me made:
Finally, make sure to backup all configuration files before any changes are made to allow for a rollback if necessary.
Microsoft Dynamics GP 2013 R2 saw the introduction of a new Workflow module which allows the approval of transactions and changes to master records. Each version of Dynamics GP since then has seen additional new functionality introduced.
I have done a fair bit of writing about Workflow since it’s introduction, both in the form of blog posts and also books, but I recently realised that one element I hadn’t written about was the enabling of a secure connection for Web Services.
Web Services for Microsoft Dynamics GP is used by Workflow for Email Notifications and Actions. The default installation of Web Services is suitable for approvals which take place within the Domain, but not for outside. This is because the default installation does not secure the connection to Web Services.
In this series, I am going to cover each of the steps required to change Web Services over to using a secure connection.
MVP Shawn Dorward has recently been taking a look at the use of custom links in Microsoft Dynamics GP. This is an area of Dynamics GP which I have never written about and, while I’ve shown it to a few clients, I don’t think any of them are actually using it.
However, as the series from Shawn shows, custom links can actually be very useful.
The links below are to Shawn’s GP Life Hacks
I wrote a blog post on Implementing Jet Reports earlier this year. While I was mid-series a new version of Jet Reports was released, Jet Reports 2018 R2.
Jet Reports published a blog post on the new features and there are some quite nice ones included.
Several items have been rearranged to be easier to find and other related items have been grouped together for a cleaner experience; all configuration settings have been combined under a single button and the run options have also been consolidated.
In an effort to better explain what they do, the Refresh and Report buttons have been renamed to Run and Run from Cache, respectively.
Details on all of the changes are available on the Jet Reports blog.