The fields available to the Workflow email notifications are very limited, and there is no front end way of making them available. I’d like to see functionality added to Workflow Maintenance to flag fields as available to the notification emails; this would include fields from any tables available to the workflow type, including from an additional table joined to the workflow type through the enhanced Query Editor.
Through enabling a Dex.ini switch, an enhanced Workflow Condition Query Editor can be enabled, which allows Dexterity tables to be joined into the workflow. However, there have been a few times recently when being able to join in a SQL View would have been most beneficial. This functionality is available in SmartList Designer where Dex tables can be selected and at the bottom of the list is a node for SQL Views which displays all of the views in the database and allows them to be selected.
I’d like the same functionality made available to Workflow Maintenance to add flexibility to workflow design.
I have worked on a number of projects for clients implementing Workflow 2.0 where being able to set one step with multiple parents would greatly reduce the work involved in creating the workflow.
For example I have recently worked with a client who has a Function segment in the chart of accounts, which requires approval by the Function Approver, which is a different person for each Function, and then a second level of approval by a Finance Panel, which is always the same five people.
When we create the workflow for POs we need to create forty Steps, one for each Function with it’s set of approvers, and then forty Finance Panel Approval Steps after each of the Function approval steps.
Step for Function = "IT" followed by a Finance Panel approval step. Step for Function = "HR" followed by a Finance Panel approval step. Step for Function = "TRAINING" followed by a Finance Panel approval step. Step for Function = "SALES" followed by a Finance Panel approval step. Step for Function = "ADMIN" followed by a Finance Panel approval step. Step for Function = "OPERATIONS" followed by a Finance Panel approval step.
If we could define the Finance Panel step and assign it to follow multiple steps instead of only the one parent which can be assigned at the moment, it would save so much time and effort when creating and maintaining the workflow.
MS Connect Suggestion: Allow Parenthesis in Workflow Step Conditions
I would like to request the facility to use parenthesis in Workflow Step Conditions in order to simplfy the creation of the conditions.
For example, currently a condition may need to be entered as:
VendorClass = “EU” and ItemClass = “IT” and CostCentre = “NEWCASTLE”
VendorClass = “EU” and ItemClass = “IT” and CostCentre = “LONDON”
VendorClass = “EU” and ItemClass = “IT” and CostCentre = “EDINBURGH”
And that is with only an or clause on one of the parameters. I might have 6 VendorClasses and 20 ItemClasses; it gets real big, real quick.
If parenthesis could be used, as in a mathematical equation, I could enter the condition as:
VendorClass = “EU” and ItemClass = “IT” and (CostCentre = “NEWCASTLE” or CostCentre = “LONDON” or CostCentre = “EDINBURGH”)
This would shrink the amount of work required to create anything but the simplest of workflow processes enormously.
Currently, the payment selection process only allows vouchers issued in the batch currency to be selected and added to the check run. If the user wants to add foreign currency vouchers, he/she needs to use the Edit Checks window to add such vouchers. It would be nice to be able to have an option to include functional currency vouchers in the case of a foreign currency batch, or foreign currency vouchers in the case of a functional currency batch.
This is the use case:
|Vendor A||Invoice 1||CA$10.00|
|Vendor A||Invoice 2||US$20.00|
|Vendor A||Invoice 3||US$30.00|
If a payment selection is performed and the batch currency is CA$, only the first voucher will be selected. To add Invoice 2 and 3, you would have to use the Edit Checks window to include both vouchers.
Conversely, if the batch currency is US$ and the payment selection for vendor A is performed, only invoices 2 and 3 would be selected and you would have to use the Edit Checks window to include Invoice 1.
What Mariano would like to see is all invoices selected (based on selection rules) and let the user deal with the exceptions, as it should be.
As mentioned, all the logic is already there via the Edit Checks window and it would be nice to incorporate as part of the payment selection process. As others have mentioned, having multicurrency vouchers included could be a payables configuration item or simply an additional option in the Select Payments (Select Checks) window.
Mark Polino has also suggested that this functionality be optioned with Rod O’Connor further suggesting the option be on the Select Checks window itself to allow maximum flexibility. Both of these seem like a good addition to Mariano’s idea.
The suggestion can be voted on here.
On the Inside Microsoft Dynamics GP blog, Pam Misialek has announced the availability of Microsoft Dynamics GP 2016 R2.
You can download it from here.
You can read about the new features coming in my Dynamics GP 2016 R2 Feature of the Day series of posts.
Pam highlights that starting next week, the Support team will post additional technical content in their Blog Series
Dynamics GP is moving, following partner and customer feedback, to annual releases. There was a recent roadmap released which you can see here.
Microsoft are currently working on GP Next and this is your opportunity to help shape the future functionality using Microsoft Connect. I would recommend you use that site to request features or enhancements which you would like to have included in Dynamics GP.
I’m about to drive home from client site, so I can’t get my hands on it for another 7 hours or so 🙁
Not having to install SilverLight on each PC or laptop which will run the web client is a definite plus; likewise it being cross platform and supported on Chrome, Safari and Firefox is another plus.
The HTML5 web client is also, in my opinion, quicker than the old SilverLight one.
However, there is one large negative which escaped me when doing initial testing and which Belinda Allen pointed out, although not on her blog, you can only have one open at a time; when you open a window the area pages are disabled, preventing you from opening another:
You can still drill down to other windows so you can for example drill from the Account Summary Inquiry to the Detailed Summary Inquiry or from Vendor Maintenance to Country Code Maintenance:
When you do open one window from a drill down the original window is then disabled. To toggle between them you need to use the Search for a Form or Report window:
This situation has created a bit of an outcry at Microsoft asking that they do further work to allow multiple window to be open at the same time. There is a post on the Microsoft Connect site where you can vote on this issue and impress upon Microsoft the importance that a resolution is found for this issue. You can vote here.
One of the main issues with the approach Microsoft have taken is that some ISV products rely on having more than one window open at the same time; another is it can seriously interrupt your workflow by being restricted to one window. Imagine, you’re half-way through creating a new vendor card when a customer rings up with an invoice query; you’d need to close the Vendor Maintenance window to open the Transactions by Debtor one.
There was a recent discussion about Multi-Dimensional Analysis (MDA) and Analytical Accounting (AA) between a group of Microsoft MVPs for Microsoft Dynamics GP; this group involved people from at least three continents and resulted in a fairly unanimous opinion that Multi-Dimensional Analysis was a useful module.
More useful in many ways than Analytical Accounting which was intended to replace it. The problem being that while MDA was fairly simple and easy to use, AA was fairly complex and clunky. While the reporting options for AA are more comprehensive than MDA, they are still not up to the standard of much of Dynamics GP itself.
To this end a suggestion has been logged on Microsoft Connect which we would appreciate you voting on. Suggestions on MS Connect with a lot of votes stand a good chance of being included in a later version of Microsoft Dynamics GP.
Please visit and vote on this suggestion.
I have submitted a suggestion to Microsoft Connect which I would appreciate people voting for. The issue is that Microsoft Dynamics GP Fixed Asset Management only supports depreciation over a 99 year life; in the UK property/land can need to be depreciated over 125 years (or sometimes even longer).
As GP doesn’t support this, clients are often reluctant to use the Fixed Assets module as they will have to handle the long-life assets in Excel and they commonly take the view that they might as well do all assets that way so that they are all stored in the same place.
Updating GP to support three character years would be of great benefit and allow assets to be depreciated over the correct life span. Please take a look and vote on this suggestion.
I realise this probably won’t interest the American readership, but I would appreciate it if you could vote for an MS Connect suggestion I have logged for Management Reporter.
In Management Reporter there is no way to change the default page setup except by editing each Report Definition.
This is an issue in the UK because the default page size here is A4 rather than Letter (as is common in the US). This means that every single new report created needs to be edited to have an A4 page size.
I think it would be incredibly useful if there was a global page setup which could be defined and would be the default for every single new report created in Management Reporter. Not only would it allow for a default page size, but also allow for a global default margin size or to choose between portrait and landscape as the default orientation.
If you think this suggestion is a good one, then please vote here and tell Microsoft how many people would benefit.