Microsoft Dynamics GP Macros: Recording A Macro

● Ian Grieve ●  ● 0 Comments   ● 

Microsoft Dynamics GPIn this series I am taking a look at how macros can be used to update data in Microsoft Dynamics GP.

Recording a macro is a fairly simple task, but I strongly recommend knowing the exact series of steps to be recorded, before starting to record the macro. I usually take a couple of practise runs before hitting record.

One of the common uses of macros for clients is to reset passwords when upgrading Microsoft Dynamics GP; due to versions of Windows and SQL Server supported by Dynamics GP, new servers are involved so these have different names (and the server name is used during encrypting the passwords.

So, in this series of posts, I am going to use resetting passwords as the example.

Macros are capable of opening and closing windows, but when resetting passwords this isn’t necessary so, before starting to record the macro, open the User Setup window (Administration >> Setup >> System >> User).

To record this macro, I am going to perform the following steps:

  1. Type a User ID.
  2. Type a new Password.
  3. Repeat this password in the Confirm Password field.
  4. Click Save.

To start recording the macro, click the Tools button on the action pane, then expand the Macro menu and click Record…:

User Setup

Continue reading → Microsoft Dynamics GP Macros: Recording A Macro

● Categories: Dynamics, GP, Microsoft ● Tags: , , , ,  ● Permalink ● Shortlink ●

MDGP 2018 RTM Feature of the Day: Rename Payment Run Windows

● Ian Grieve ●  ● 0 Comments   ● 

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2018 RTM; as the most recent versions have been, these posts are in the form of PowerPoint slides; I am reposting them here so they can be read more easily as well as adding my own commentary.

The series index for this series of posts is here.

The ninth Feature of the Day is a feature requested by Mariano Gomez and that is to rename the payment run windows.

So instead of them being named Check or Cheque, depending on the installed language pack, they will now be named Payment:

Purchasing menu

The windows which have been renamed are:

  • Select Payables Checks -> Build Payments Batch
  • Edit Payables Check Batch -> Edit Payment Batch
  • Edit Payables Check -> Edit Vendor Payment
  • Print Payables Checks -> Print Payment Documents
  • Post Payables Checks -> Post Payment Documents

In the UK, virtually no-one uses cheques anymore; payments are made by BACS which is a form of EFT. Renaming these windows

Click to show/hide the MDGP 2018 RTM Feature of the Day Series Index

● Categories: Dynamics, GP, Microsoft ● Tags: , , , , , , ,  ● Permalink ● Shortlink ●

Microsoft Dynamics GP Macros: Limitations of Macros

● Ian Grieve ●  ● 1 Comment   ● 

Microsoft Dynamics GPIn this series I am taking a look at how macros can be used to update data in Microsoft Dynamics GP.

Macros can be a quick and easy way of inserting or updating information in Microsoft Dynamics GP, but there are some limitations to macros which need to be considered before using them.

A macro works by recording the exact series of actions taken by the user after clicking record; this means it is best to practise the series of steps the macro should record before clicking record.

When the macro is played, it repeats the exact steps as recorded. The way I typically explain this to clients, is to say that the macro pretends to be them typing very quickly. Which is a fair description of what the macro does; it records any typing and then plays back the typing; depending on what actions were recorded in the macro, you will see windows open and close and fields typed into.

This means that when a macro is being played back, Microsoft Dynamics GP must retain cursor focus or the macro will crash.

A macro plays back the exact steps as recorded and does not tolerate any deviation; this means that if the macro plays back and encounters a difference, such as a popup message dialog, the macro will crash and stop running. Any data updated will remain updated, so restarting the macro will likely require updated data to be removed from the macro file.

A frequent question asked by users is if they can build in conditions within the macro. The short answer is no, you can’t as macros simply play back a series of steps. There is a longer answer which I will cover when in the posts on producing a macro from a macro template using Excel and SQL.

When recording a macro which will open windows, it is best to use the drop down menus at the top to open the window, as using the area page menu will often fail as this used the exact mouse position; when users using the same macro have different access configured, the menu option will be in different locations and therefore cause the macro to fail.

Click to show/hide the Microsoft Dynamics GP Macros Series Index

Microsoft Dynamics GP Macros
Limitations of Macros
Recording A Macro
● Categories: Dynamics, GP, Microsoft ● Tags: , , , ,  ● Permalink ● Shortlink ●

MDGP 2018 RTM Feature of the Day: New Workflow Functionality – Reporting for Workflow

● Ian Grieve ●  ● 0 Comments   ● 

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2018 RTM; as the most recent versions have been, these posts are in the form of PowerPoint slides; I am reposting them here so they can be read more easily as well as adding my own commentary.

The series index for this series of posts is here.

The eighth Feature of the Day is new Workflow functionality; I am going to break this feature down into three posts, as the three features included by Microsoft are, while all Workflow enhancements, unrelated to one another.

The third piece of new functionality is the reporting for Workflow. This report is located on the Administration area page, under reporting as Workflow History.

Users can filter by the following:

  • Workflow type.
  • Workflow approvers.
  • Workflow status
  • Approval date
Workflow Maintenance

Workflow comments can optionally be included on the report.

Click to show/hide the MDGP 2018 RTM Feature of the Day Series Index

● Categories: Dynamics, GP, Microsoft, Workflow ● Tags: , , , , , ,  ● Permalink ● Shortlink ●

MDGP 2018 RTM Feature of the Day: New Workflow Functionality – Copy Workflow Steps

● Ian Grieve ●  ● 0 Comments   ● 

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2018 RTM, as the most recent versions have been, these posts are in the form of PowerPoint slides; I am reposting them here so they can be read more easily as well as adding my own commentary.

The series index for this series of posts is here.

The eighth Feature of the Day is new Workflow functionality; I am going to break this feature down into three posts, as the three features included by Microsoft are, while all Workflow enhancements, unrelated to one another.

The second piece of new functionality is the ability to copy a Workflow step; this is one of the suggestions I made on MS Connect, so it’s nice to see it added in this version.

This piece of new functionlity enabled the Copy button on the Worklflow Maintenance window when a step is selected:

Copy Workflow Step

In the Copy Workflow Step window, you are able to select a new step for the Workflow Step as well as marking a box to copy the Sub Steps.

This will save so much tiem when creating a new Workflow process. With the lack of parenthesis in Workflow Step Conditions (please vote on my MS Connect Suggestion to add them) creating steps with complex, or even just numerous, conditions can be a lengthy process; having to do this for multiple steps can make the creation of workflow a real chore, but this new functionality, especially with the abilty to include sub steps (which goes beyond my suggestion and is a great idea so kudos to Microsoft for that) will save so much time.

You can easily copy steps and then edit the step condition which is different between the steps (often somthing like a cost centre).

Click to show/hide the MDGP 2018 RTM Feature of the Day Series Index

● Categories: Dynamics, GP, Microsoft, Workflow ● Tags: , , , , , ,  ● Permalink ● Shortlink ●

MDGP 2018 RTM Feature of the Day: New Workflow Functionality – Reminder Emails

● Ian Grieve ●  ● 0 Comments   ● 

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2018 RTM, as the most recent versions have been, these posts are in the form of PowerPoint slides; I am reposting them here so they can be read more easily as well as adding my own commentary.

The series index for this series of posts is here.

The eighth Feature of the Day is new Workflow functionality; I am going to break this feature down into three posts, as the three features included by Microsoft are, while all Workflow enhancements, unrelated to one another.

The first of the new functionality, are reminder emails. Reminder emails can be configured on a per step basis in a similar way to the Time Limit:

Workflow Maintenance

Continue reading → MDGP 2018 RTM Feature of the Day: New Workflow Functionality – Reminder Emails

● Categories: Dynamics, GP, Microsoft, Workflow ● Tags: , , , ,  ● Permalink ● Shortlink ●

Microsoft Dynamics GP Macros: Series Index

● Ian Grieve ●  ● 3 Comments   ● 

Microsoft Dynamics GPUsually when integrating data into Microsoft Dynamics GP we will use Integration Manager, but sometimes this tool is either not available or suitable. Not all clients have a licence for the Customisation Pack (which includes the licence for Integration Manager) or the data to be imported does not have an available adaptor in Integration Manager; examples of the latter which I’ve done work with recently include Bill of Materials and Extended Pricing.

The alternatives to using Integration Manager include other tools such as SmartConnect or Scribe (which have their own price tags attached), direct SQL inserts (which do not respect business logic in the application) or the use of GP macros to play back actions.

This latter method is what I am going to cover in this series; I will cover the recording and playback of macros and how data can be loaded in bulk by using the recorded macro as a template.

Microsoft Dynamics GP Macros
Limitations of Macros
Recording A Macro
● Categories: Dynamics, GP, Microsoft ● Tags: , , , ,  ● Permalink ● Shortlink ●

Missing Security Roles In Microsoft Dynamics GP 2018 RTM

● Ian Grieve ●  ● 0 Comments   ● 

Microsoft Dynamics GPThe Dynamics GP Support and Services Blog has a post on the missing security in Microsoft Dynamics GP 2018 RTM; this is the new security roles and tasks created for the new functionality.

For features which are being enhanced, the new security tasks may be being added to roles which already exist and are assigned to users, the security is not automatically updated with the upgrade, but instead scripts are made available to add the missing security; this places the onus on the client to determine if the roles should be updated or not.

I have updated my original post with the new script, but you can also download it here.

● Categories: Dynamics, GP, Microsoft ● Tags: , , , , , ,  ● Permalink ● Shortlink ●

MDGP 2018 RTM Feature of the Day: Workflow Additional Fields

● Ian Grieve ●  ● 0 Comments   ● 

Microsoft Dynamics GPThe Inside Microsoft Dynamics GP blog has started a series Feature of the Day posts for Microsoft Dynamics GP 2018 RTM; as the most recent versions have been, these posts are in the form of PowerPoint slides; I am reposting them here so they can be read more easily as well as adding my own commentary.

The series index for this series of posts is here.

The seventh Feature of the Day is Workflow Additional Fields. Back in April 2017 I submitted an MS Connect suggestion asking for the ability to add additional fields to Workflow.

I guess this might be a form of responding to this suggestion, but I was looking for a way that the user could determine which fields could be available rather than Microsoft deciding which extra fields are added.

Two of the workflow types have had extra fields added where they available in both the Workflow Condition Editor and Message Setup windows allowing you to build workflow steps and notification emails with them.:

Two other workflow types have had the Account Description made avaiable at the line level. These two workflow types are:

  • Purchase Order
  • Purchase Requisition

While having the extra fields available is good, I am disappointed with this new feature for two reasons.

Firstly, it is a very limited number of fields which have been made available rather than allowing users to select additional fields to add.

Secondly, from everything I have seen on the feature regarding EFT information, it only seems like you can include the fields in the workflow conditions and email messages; Dynamics GP is desperately missing functionality around changes to EFT details needing to go through workflow for approval. I fear that this new feature doesn’t extend this far.

As soon as Dynamics GP 2018 is released, I will be giving this a test to confirm how it works.

Click to show/hide the MDGP 2018 RTM Feature of the Day Series Index

● Categories: Dynamics, GP, Microsoft, Workflow ● Tags: , , , , , ,  ● Permalink ● Shortlink ●

SQL Function To Return Last Workflow Comment

● Ian Grieve ●  ● 0 Comments   ● 

Microsoft Dynamics GPBack in April 2017 I posted an SQL function which can be used to return the workflow status of a transaction or card. This function is now complimented by another one which can be used to return the last comment recorded. This was created for use on a customisation of the Purchase Requisition Entry window which added a Rejection Reason field so users could see at a glance why a purchase requisition had been rejected.

IF OBJECT_ID (N'uf_AZRCRV_GetWorkflowApprovalComments', N'FN') IS NOT NULL
    DROP FUNCTION uf_AZRCRV_GetWorkflowApprovalComments
GO
CREATE FUNCTION dbo.uf_AZRCRV_GetWorkflowApprovalComments(@WorkflowTypeName CHAR(50),@WfBusObjKey CHAR(20))
	RETURNS VARCHAR(14)
AS
/*
Created by Ian Grieve of azurecurve|Ramblings of a Dynamics GP Consultant (http://www.azurecurve.co.uk)
This code is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International (CC BY-NC-SA 4.0 Int).

Returns Workflow Approval status of a specified workflow item.

Requires input parameters of WorkflowTypeName and WfBusObjKey

Valid Workflow Type Names are (as of Microsoft Dynamics GP 2016 R2):
	General Ledger Batch Approval
	Receivables Batch Approval
	Payables Batch Approval
	Payables Transaction Approval
	Purchase Order Approval
	Purchase Requisition Approval
	Vendor Approval
	Employee Profile Approval
	Employee Skills Approval
	Payroll Direct Deposit Approval
	Payroll Timecard Approval
	Payroll W4 Approval
	Expense Report Approval
	Timesheet Approval
	Smartlist Designer View Approval
*/
BEGIN
	RETURN ISNULL((
		SELECT TOP 1 
			WF30100 AS ['Workflow History']
		FROM 
			WF30100 AS ['Workflow History']
		INNER JOIN
			WFI10002 AS ['Workflow Master']
				ON
					['Workflow Master'].WorkflowInstanceID = ['Workflow History'].WorkflowInstanceID
		WHERE
			['Workflow Master'].Workflow_Type_Name = @WorkflowTypeName
		AND
			['Workflow Master'].WfBusObjKey = @WfBusObjKey
		ORDER BY
			['Workflow History'].DEX_ROW_ID DESC)
	,'Not Submitted')
END
GO
GRANT EXECUTE ON uf_AZRCRV_GetWorkflowApprovalComments TO DYNGRP
GO

This function can easily be included in a view or other query used in a variety of reporting tools.

● Categories: Dynamics, GP, Microsoft, Workflow ● Tags: , , , , , , ,  ● Permalink ● Shortlink ●