By: Pam Burnham, Director of Product Strategy 

Do you have inventory to track? 

Instead of an investment in an independent Warehouse Management System (WMS), consider the functionality already available in your current Dynamics GP investment. In this article, we want to introduce you to one of the features that can transform your GP environment into an embedded WMS:  Multiple Bin Tracking.  A feature that will allow you to maintain GP as your single system of truth.

We get moans from partners and customers both when we initially bring up this topic. Understandable since it does carry a lot of extra overhead if you do not have the tools in place, such as our PanatrackerGP solution, to support it. But those looking for a WMS solution are looking for this specific function which allows you to know where exactly the inventory is located and how much you have. When you add the ability to record the inventory transactions at the time and point the inventory is handled, it isn’t necessary to use a separate system that requires reconciliation overhead.

General Multiple Bin Configuration Overview

When you enable multiple bin tracking (Panatracker tips on bins), you then enable the ability to set up bin locations under each of your sites. You need at least one bin defined per site. If you have sites that are virtual or you don’t need multiple bin locations configured, you simply set a single bin, we recommend naming the same as the site.  Bin setup in GP is flexible. If you determine later that a site requires more bin locations, there is nothing stopping you from adding more.

The additional bin set up in GP includes the ability to set a default bin. These default bins can be configured on either a Site or Item+Site level. Transactions Impacted Include

• Purchase Receipts
• Purchase Returns
• Sales Order Fulfillment
• Sales Returns
• Assembly Receipts
• Material Issues
• Manufacturing Receipts
• Repair Issues

Setting up these defaults can save you the time required to manually select bins when inventory transactions are entered directly into GP. Using a solution like PanatrackerGP will put the ability to capture and enter transactions on the warehouse floor; inventory control has never been easier.

Priority Bin Setup Adds Min and Max Logic

In addition to the bin default assignments, there is also set up for the Priority Bins. The priority bin setup is on the Item + Site level. In addition to defining what bins to configure as priorities for each item, a min and max quantity assignment can be set up. Great tool for restocking reporting. You can set up as many priority bins as you need for each item and site combination. We recommend setting Priority 1 to match the item Sales Order Fulfillment default since this would represent your primary stock bin location.

Obtain Access to Real-Time Available Inventory

Another great advantage of moving to multiple bin tracking in GP is more true reporting on your available quantity.  If you use Sales Order Processing in GP and allocate your inventory, you know that the On Hand – Allocation = Available inventory. But it doesn’t really represent what you truly have in stock at any given point and time. On a site level, it is typically a number between the On Hand and Available at any given point. This is primarily due to delays in the posting of the sales order invoices. So the order may be picked and shipped, but GP is still showing the inventory as On Hand until the invoice (or any other inventory transactions) are posted.

By using a separate fulfillment process on sales orders with multiple bin tracking, the inventory is taken out of available at the bin level … when the inventory is removed for fulfillment and shipping. Bin level quantities end up being true to real-time giving you great inventory management. This is an added bonus to the fact that you also give the order pickers access to see exactly where the inventory is and the respective bin inventory levels.  If using PanatrackerGP, bins with available inventory are automatically defaulted for the user for a ‘guided’ pick process making it even more streamlined.

Add More Tracking Logic with Advanced Bin Management

We feel that GP provides a great foundation for inventory location tracking with the multiple bin infrastructure. We have built on that foundation to take it to a WMS level with our Advanced Bin Management module. This extends the bin infrastructure to support defining a bin type. Bin types include:

• Stock
• Overstock
• Staging
• License Plate

With bins defined to these categories, we can add more advanced logic. For example, you may not want order pickers to default to an overstock bin if it requires a lift truck to reach the items. If inventory is ‘staged’ for another order, you don’t want those bins available to other order pickers.  The license plate bin is a ‘moveable’ bin that represents grouping inventory to be moved as a single unit. By defining the bin as this type allows us to enable this additional logic for WMS-like inventory control.

More Precise Reconciliation of Physical Counts

Another advantage of multiple-bin setup in GP is set up and managing stock count functions. By having more specific locations to count against. If you count against an item in one general site, you need to complete the count against the entire site before you can reconcile. With bins, inventory transaction activities can be resumed faster since your count is against the Site + Item + specific Bin.

Turn MSDGP To Your Fully Integrated WMS

Multiple bin tracking is a coveted feature of a WMS and already exists within your Dynamics GP environment. Panatrack can guide you in setup and the migration path to using this feature. The PanatrackerGP solution turns multiple bin tracking into an effective tool to streamline your inventory tracking and adding the control you need.

Contact Panatrack for more information or to schedule a demo!

Microsoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

The deployment of the Excel Reports is is done via Reporting Tools Setup (Administration area page >> Setup >> System >> Reporting Tool Setup). Click the Excel Reports tab.

Change the Location to Network Share. Reports Directory can be set at both the System Level (for the out of the box reports) and User Level for customised reports.

You can also set a subfolder for where the reports are to be deployed; this is useful when you have more than just the Microsoft Dynamics GP reports deployed onto the report server.

Make sure the checkboxes in the Deployment Options section are checked and click the Deploy Reports button.

Click Yes to confirm the dialog to save changes:

Click the Deploy Reports button again and the deployment will start. This may take a couple of minutes to process, but a dialog with a progress bar will display:

Once the deployment has completed, the Deployment Options box will show success with green marks:

Click to show/hide the Hands On With MDGP 2018 RTM Series Index

Read original post Hands On With MDGP 2018 RTM: Deploy Excel Reports at azurecurve|Ramblings of a Dynamics GP Consultant

Sharing "My Views" with Teams

In Part One, I talked about the differences between System Views and My Views. I also mentioned that whenever possible to filter by dynamic values (current user, manager, territory, last month, next year, etc.).

What if you work for a company that has several different divisions and your user base works across multiple divisions? They would want to have access to their views but they don't necessarily have to see all of the views for all of the other divisions. Depending on the different divisions or departments, you could end up with over 100 different views!

In the end, you will still have a lot of views but they won't be visible to all users all the time. As the system administrator, you will have access to all of the views but since you're sharing the views with teams you only have to maintain the team members and not the views.

Let's Get Started!

The first thing you need to do is setup Teams. They are very easy to setup and are very easy to maintain. In D365, go to Settings | Security | Teams. Create a new Owner Team (give it a name, add it to a business unit, assign it an administrator, and select a queue). After you save your team you can now add users to it. Add any users who fall under this team. The great thing about teams is that one user can be in multiple teams. Any new users you add in the future can be added to teams directly from their user record. You can save yourself a few clicks this way!

For an example, think about a car dealership with different divisions for different makes of cars. User A could be a member of the Ford and Toyota team where User B is just a member of the Jeep team.

As the system administrator, you will have to setup all of the views for the different divisions and share them accordingly. Two things to keep in mind to save time:  #1, you can setup the first view, save it, and then use Save As to 'copy' it and #2, you can share multiple views at the same time.

Sharing Your Views

In the Advanced Find popup window, click on 'Saved Views'.  This will give you a list of all of your saved views for the selected entity. Click on the List Tools, Saved Views tab (if necessary). You can select a different Record Type here as well. Select the view(s) that you want to share with a specific team and click the Share button in the ribbon. In the Share saved view window, click on Add User/Team from the left, select Team as the record type, select your team, click OK, and then click Share. You can choose different permissions as well, but I recommend only giving Read access to these views.

As an admin/creator of the views, you will see everything when you access the views from the entity:

User B, who is only a member of the Jeep team, will only see the views shared with the Jeep team:

User A, who is a member of the Ford and Toyota teams will see the views shared with those teams:

System Views or My Views?

This is a question you will have to answer yourself. Do you have hundreds of different system views? Can they be minimized by using dynamic filtering? If you legitimately need to have a lot of different views then sharing with teams may be the way to go. It takes some time to setup initially, but going forward, when you setup a new user, all you have to do is add them to the appropriate team(s) and they inherit all of the views shared with that team. As an added bonus, since these are 'Owner' teams, you can even assign records to these teams in CRM as well.

Beringer Technology Group, a leading Microsoft Gold Certified Partner specializing in Microsoft Dynamics 365 and CRM for Distribution. We also provide expert Managed IT Services, Backup and Disaster Recovery, Cloud Based Computing and Unified Communication Systems.

The post System Views vs My Views – Part Two of Two appeared first on CRM Software Blog | Dynamics 365.

Dynamics GP 2017 Year End Changes will include the following -

1. No W2 or W3 form changes this year
2. There are EFW2 changes
3. The year-end update will have some product quality fixes delivered
4. Affordable Care Act (ACA) is still alive and well – the required form changes will be part of the year end update
5. Depreciation changes mostly around luxury auto depreciation

GP 2013

Remember if you are on any version of Dynamics GP 2013, mainstream support will end on April 10, 2018, after which time you will no longer receive tax and year end updates, nor will you receive any further product updates to GP 2013. Time to upgrade.

All Versions

All year-end updates are scheduled to be released the week of November 20, 2017. To install the year end update, you will need to be on one of the following versions:

• GP 2013 – Must be on version 12.0.2104 or later
• GP 2015 – Must be on version 14.00.0983 or later
• GP 2016 – Any version
• GP 2018 – Any version

Microsoft does require you to install the year end update this year, as if you do not, your ACA forms will be wrong and your EFW2, electronic files will fail, along with fixed asset depreciation being incorrect.

If you do not use any of these areas, you may be able to skimp by without applying the update.

For more information contact Tridea Partners today!

This article was written by Tridea Partners, a leading Microsoft Dynamics partner.

Dynamics 365 for Field Service is used by organizations to have better visibility and control of their resources, such as technicians, or equipment that they use for service calls. In this episode of Dynamics 365 In Focus, D365 University Trainer, Tad, will take you through the top reasons why your organization would benefit by taking our Dynamics 365 for Field Service training course. For more information about this course, register for our live PO TV webcast for a preview of the content, and then check out our D365 University page to see when the course is available.

Layering vs. Extensions: what are they and how are they different?

In a review of Dynamics 365 Extensions, it’s important to begin by becoming familiar with the most recent version product names. In this article, we are specifically referring to Dynamics 365 for Finance and Operations – Enterprise Edition, which was previously called Dynamics AX. The next version released after Dynamics AX 2012 was Dynamics AX 7 which was then rebranded as Dynamics 365 for Finance and Operations.

With the evolution of Microsoft Dynamics through these versions over the past five years, significant milestones have been achieved and the development platform is no exception. We’ll dive more deeply into these changes and discuss the benefits that your organization can reap by using the latest development tools to customize the out-of-the-box system.

The Dynamics AX user community is very familiar with the customization concept called layering. While there are several key benefits of layering, the three types of cost - time, expense and risk - cannot be overlooked. The next generation of customization, known as Extensions, now available for Dynamics 365 for Finance and Operations – Enterprise Edition, replaces layering as the environment that developers can now use to extend the core functionality.

In a future article, we will provide more detail on the Extension model and how it overcomes some of the challenges faced by organizations using the layering model with Dynamics AX.

How did layering work in Dynamics AX?

Dynamics AX has been available since the late 90’s and was always very well-known for its customizable platform. Its proprietary programming language X++ was easy to learn as it was similar to Java or C++ and it required similar skills. This meant that modifications were easily executed in a Dynamics AX environment. A selling point for Dynamics AX has always been its ability to enable developers to get started very quickly.

The concept of over-layering meant that third-party software companies and value-added resellers could also take the Microsoft code and change it to do whatever the customer needed. The code was not as freely available as Open Source; but, for a fee, both developers and ISV partners could access the code base of Dynamics AX and make transformative changes.

For example, let’s consider a sales order object, which contains tables, classes, and methods. Developers could take the code from Microsoft for these objects and insert their code directly into the relevant area of the object’s code - you could interrupt it, shut it down, or extend it to take any action that was required to meet the customer’s business logic.

The ‘layers’ were segregated into the following levels:

• System layer – Microsoft Dynamics AX code.
• ISV layer – Approved Microsoft software vendors could modify System layer in the ISV layer.
• VAR layer – Implementers could modify both the ISV and the System layer in the VAR layer of code.
• Customer layer – Developers from the customer’s organization could modify code from all three layers above to meet the needs of their business.

This model gave customers enormous flexibility by allowing them to make changes to any of these layers. All layers in the model are visible with the code, with the highest layer as the one being executed. This layering concept gave the customer the ability to ensure the system behaved in exactly the manner that was required.

But these benefits came at a cost …

While all of this flexibility sounds good, there was a problem, and a very costly one at that. Companies that customized the code in their layers extensively got ‘version locked.' This means that they were not able to upgrade to the latest version of the ERP software without spending a huge amount of time and money on development resources to bring all of their customizations up-to-date.

If Microsoft issued a service pack or a product update, organizations were not able to access these updates unless all layers in the model were updated and reprogrammed to consume or not conflict with the new Microsoft code in the system layer.

For example, companies using an ISV layer could not accept any updates from the system layer until the ISV had made the investment to analyze, refactor and reprogram their code to work with the Microsoft update in the system layer. Each layer owner is required to determine where all the conflicts may exist and update the code to ensure that it functions correctly across all the layers.

The costs of this process should not be underestimated.

It’s expensive. The development/testing process and the process of putting new code into production can be extremely high. Additional developers and consultants are required to ensure that all of the code is updated and working seamlessly with every other part. Often, these ‘mini-implementation’ costs are only adding a series of patches to the solution with no additional value-added functionality to drive a positive ROI.

It takes time. Ensuring all the layers are updated can take a considerable amount of time as each layer has an owner who may not make the changes in a timely manner.

It’s risky. A customer using an ISV application in which the ISV is not adequately resourced to make the required changes to their code adds risk to your business, as no changes can be made until the ISV layer is updated. This is especially risky for mission-critical functionality.

In summary, the layering model worked well for the implementation and management of customizations, but maintaining them and moving them to a newer version was expensive, time-consuming, and risky. The implementation of updates or patches became their own mini implementations which resulted in companies becoming version-locked very quickly.

While the Dynamics AX community has lived with these challenges for about 15 years, the launch of Dynamics 365 brings a new model for customizations, called Extensions, to Dynamics 365 for Finance and Operations – Enterprise Edition.

The Extensions model enables any organization to customize the functionality of Dynamics 365 by creating side Extensions and thereby making no changes to the core system code. This new model avoids version-locking and allows organizations to remain current on their Dynamics 365 version without having to invest in significant development and consultancy resources.

In a future article, we will discuss the details of the Extensions model in more depth. For more information on getting started with Dynamics 365 for Finance and Operations, don’t hesitate to contact our team of Microsoft Dynamics experts.

The June release for Dynamics AX 2012 R3 version is now available in LCS on the updates tile inside your R3 project. This update represents a typical collection of smaller functional improvements and technical fixes.  Bugs were fixed in all areas with enhancements found in Warehouse & Transportation, Retail, DIXF, APAC & Europe localizations and Project Accounting. Please see the full list of hotfixes below to search for your specific issue newly included in this release. This release is a cumulative package including all other fixes released in the prior CU13 update. This release is intended to give visibility into fixes recently shipped for R3, including some features and design changes that are newly released in this month.

Here are a few details related to this release:

• Primary Build: 6.3.6000.3090
• Number of Application hotfixes: 292
• Number of Binary hotfixes: 52

Details of the install process can be found here: https://technet.microsoft.com/en-us/library/hh538446.aspx#PackageR3

What is included in this month’s release?

Design Change Requests, Feature Requests & RegFs

Fixes Released

Lets take a look at service agreements. DynaRent automates the service management cycle beginning with the initial request through scheduling, monitoring, and invoicing. At the same time, it offers planners complete, real-time overviews. They gain the ability to overview equipment. Furthermore, they have the tools to tailor and service orders at the drop of a hat.

You can use DynaRent’s service agreements and subscriptions to define the resources used for a typical service visit. It is possible to define how you invoice those resources, spare parts, and other expenses to the customer. In addition, a service agreement can specify standard response times, and serve as a dynamic record for recording actual times.

DynaRent’s service-level agreements store information about the service response times that are agreed upon in a service agreement.

When service jobs are created either manually in the system or automatically using DynaRent PowerApps, DynaRent automatically takes this into account and follows up accordingly.

Image 1: Service agreement details in DynaRent for Dynamics 365 for Finance and Operations

Taking a closer look into the system and service agreements

In this overview you see all the details of the service jobs linked to standard Dynamics 365 for Finance and Operations projects. Additionally, providing the ability to link and monitor all your service requests, costs, and revenue. Also, it is easy to monitor follow-up actions and invoicing to your customers.

Image 2: Furthermore, you see here cost control on a specific service agreement

Cost control overviews provide detailed information about costs and revenue and chargeability of:

• Hours spent
• Spare parts used
• Fees
• Additional costs
• Subscriptions

Extend your service management into the field with mobile capabilities: service management work orders generate automatically, with flexibility to modify elements and timing as needed. As soon as you generate a work order, the system automatically sends it to the appropriate service tech’s mobile device.

DynaRent Mobile works with Microsoft PowerApps so that all service information and processes are synchronized across depots, devices, and business departments—making your enterprise truly connected.

Curious about our DynaRent Solution Suite? We’re more than happy to provide you with a tailored demonstration. Please contact us at info@highsoftware.com to discuss, or visit www.highsoftware.com and see what we’re up to!

Microsoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

A number of my clients use Integration Manager for loading data into Microsoft Dynamics GP; a number of the integrations are either available only with, or run faster with, the eConnect adaptor. So before Integration Manager itself can be installed, eConnect needs to be installed on the client machine.

eConnect is available through the setup utility under the Additional Products header. Before you get to select this though, you may need to click through some security warnings.

Depending on server settings, you might receive multiple security warnings during the installation; click Run on each one as it appears:

Open File - Security Warning

Accept the terms of the license agreement and click Next:

The default selected features is all that is required to install the eConnect adaptor for Integration Manager. Click Next to continue:

Enter the Domain account details under which the eConnect for Microsoft Dynamics GP 2018 Integration Service will run under and click Next:

On the ,em>SQL Connection Information step, enter the full SQL Server instance name in the Server Name field and then enter the Dynamics GP System Database name.

Click Next to continue:

Click Install to install eConnect:

Once the installation is complete, click Exit:

Click to show/hide the Hands On With MDGP 2018 RTM Series Index

Read original post Hands On With MDGP 2018 RTM: Install eConnect on Client at azurecurve|Ramblings of a Dynamics GP Consultant

Recently, we upgraded a client’s CRM 2011 to Dynamics 365. In CRM 2011 instance, there were some workflows that were using custom workflow activities. However, after the upgrade, we were getting an error in Dynamics 365 saying,“Invalid User Authorization – The user authentication passed to the platform is not valid”.

I was getting this error when I tried to open the workflows that were using the custom workflow steps, and when I tried to activate a draft workflow process.

I did some research on this issue. I couldn’t find the exact cause of this issue, and it turns out I am not the only one affected by this issue. But what I did find was a workaround for this issue. In this blog, I will walk through the steps that helped me to overcome this issue.

1. Create a backup solution of the all the workflows.
2. After the backup solution has been exported, delete the workflows that are using custom workflow activities.
3. Unregister the custom workflow activities that were added during CRM 2011 to Dynamics 365 upgrade.
4. Register those workflow activities again.
5. Import the backup solution of the workflows that was exported earlier (at step 2).

And this is it, but be sure to test the workflows. The solution above is just a workaround, but I am not a 100% sure what causes this error, and how it can be prevented.

Microsoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

If you are going to be using Integration Manager with eCOnnect Adaptors, make sure eConnect has been installed on the client before following the steps in this post.

To install Integration Manager, launch the setup utility from the installation media:

Depending on server settings, you might receive multiple security warnings during the installation; click Run on each one as it appears:

Open File - Security Warning

and, under the Additional Products header, select on Integration Manager and click Install on the popup menu:

Accept the terms of the license agreement and click Next:

Check the features being installed and the install Location and then click Next:

Click Install to begin the installation:

Once the installation has finished, click Exit to close the installer.

Click to show/hide the Hands On With MDGP 2018 RTM Series Index

Read original post Hands On With MDGP 2018 RTM: Install Integration Manager at azurecurve|Ramblings of a Dynamics GP Consultant

Microsoft Social Engagement 2017 Update 1.11 is ready and will be released in December 2017. This article describes the fixes, and other changes that are included in this update.

New and updated features

Support for Twitter's extended tweet length

With this update, Social Engagement supports the new tweet length as recently released by Twitter. When writing tweets, you benefit from the increased limit of 280 characters. As a temporary restriction, tweets with Japanese, Korean and Chinese characters will not be reflected in the character limit accurately. If your tweet is too long, you will receive an error notification and you can shorten it.

By early 2018 we plan to update our service to use the new logic of Twitter for any language and character set.

Introduction of table and pattern view for charts in Social Engagement

A new table view on all existing charts in Social Engagement is now available. This means that every user can decide whether they want to explore the data represented as charts or as tables.
You can either turn on the table view on single charts or you can enable the table view globally for your user profile in Settings > User Preferences under Chart data representation mode.

Additionally, we're introducing a new styling for charts with colored areas. You can choose to render the charts with a filling patterns or solid colors. To switch between filling pattern and solid color, go to Settings > User Preferences and update the Chart filling mode.

Redesigned activity map and pause functionality

We are introducing the "pause" functionality to the activity map feature. This enables you to choose whether you want to get live updates on the map, or not. When turned off, posts will stop updating automatically and users can view and explore a snapshot in more detail. New posts will appear again, when live updates have been are turned on and new posts are available.

In addition to that, the activity map has received a couple of visual updates, such as bigger dots on the map and updated visuals in the activity map header.

New field in the JSON payload for Azure Event Hubs: post.profile.uri

Social Engagement includes a feature that allows users to send posts to Azure Event Hubs by using Automation Rules. As part of evolving functionality, Social Engagement is updating the JSON payload by replacing the post.profile.id field with a new post.profile.uri field. Moving forward, post.profile.uri will also include a source-based identifier as part of the field value (for example: mse-tw://#12345678).

Please make sure you follow the timeline outlined in this blog post to avoid breaking your apps and intermittent data loss.

Resolved issues

In addition to the new features, Update 1.11 addresses the following issues:

• To ensure all private messages are received within Social Engagement, we have updated the mapping of the language recognition for private messages. If the system can’t identify a language in a private message, or if an identified language is not supported by Social Engagement, instead of discarding the messages, we are now mapping them to the first selected search language in Global Settings > Search Languages. This improvement especially helps in cases where a private message contains for example only numbers, such as a phone number.
• Updated Social Engagement documentation regarding Facebook Acquisition Tokens, Facebook comment actions, adding Custom Tags, and requirements for YouTube Engagement actions.

In this week's Microsoft Dynamics Partner News Roundup:

• Hitachi Solutions America launches Engage for insurance and industry specific product suite
• Ceridian to offer payroll globally with Microsoft Dynamics 365
• Acando Germany acquires Microsoft Dynamics 365 specialist Anywhere.24
• Announcing project service and field service training by PowerObjects, An HCL Technologies company
• ClickDimensions Expands Executive Leadership Team

Hitachi Solutions America launches Engage for insurance and industry specific product suite

Hitachi Solutions America, a provider of global industry solutions based on the Microsoft Clo...

read more

Microsoft Dynamics GP 2018 RTM has now been released. In this series of posts, I will be stepping through the installation of Microsoft Dynamics GP and additional products and then will move on to taking a look at the new functionality which has been introduced.

The series index for this series of posts is here and will automatically update as posts go live.

With Integration Manager now installed, the final step in it’s installation is to run it and enter the license key.

It is important that the first time Integration Manager is launched, you do so by right clicking and selecting Run as Administrator; this ensures that Integration Manager has sufficient privileges for writing the necessary registry entries.

When Integration Manager starts, you will be presented with a Register Now/Later window; to use Integration Manager, a licence key must be entered, so click Register Now:

In the Integration Manager Registration window, enter your Site Name and Registration Keys:

Click OK to save the key; the main window of Integration Manager will be displayed with the application now ready for use.

NB: As of the time of writing, the GP 2018 registration keys are not yet available.

Click to show/hide the Hands On With MDGP 2018 RTM Series Index

Read original post Hands On With MDGP 2018 RTM: Integration Manager First Run at azurecurve|Ramblings of a Dynamics GP Consultant