Monthly Archives: April 2019

INET Dynamics

3 Tips to Boost  Dynamics 365 for Finance and Operations Performance

 

Categories: Dynamics 365
Tags:

 

Dynamics 365 for Finance and Operations (D365FO) is an ERP software targeting for large enterprises. The product offers both cloud and on-premises options. Such a complex system serves a huge number of users with hundreds to thousands of actions each day. Without proper monitoring and tuning of the system, organizations might face slowness and performance issues.

 

The needs for performance testing and boosting of each company is different depending on their own business and as a result, their areas of large work volume. In this article, we would like to share some common tips which are all out of the box features of  D365FO to boost the performance.

Batch jobs to boost SQL performance:

In D365FO, SQL performance can impact performance in various scenarios. The system provides two notable system batch jobs that help to compress database and rebuild fragmented indexes.

 

First, with a large enterprise, database volume can grow very quickly, which leads to the needs of data volume management. Database compression offers some key benefits of storage requirement reduction, query performance and faster time to recover if needed. The feature is now introduced in the application that you can configure and run from the client.

 

Second, index fragmentation is another issue that grows over time and decreases performance. You can check your environment index fragmentation from LCS portal by navigating to Environment Details page > Environment monitoring > SQL Insights > Queries > Get fragmentation details >  Execute.

The system batch job for SQL defragmentation is introduced from Platform Update 22 so you can configure a regular job to rebuild indexes at your preferred time.

 

Overall, the two system batch jobs are available automatically for the whole system, not specific to a legal entity. Our recommendation is to keep it as default and not tempted to change other parameters like company, created by and run by except for the recurrence of the job. Microsoft recommendation from the official document is to run the job at least once a week.

 

Some other parameters that can be configured are how long the job will run, how many the indexes are rebuilt and DTU threshold. The threshold ensures the job is not run when the system is too busy. For example, with the parameters in the below screenshot, the rebuild index batch job will only run for 120 minutes and target 500 indexes, however, if the DTU level is higher than 50% at the scheduled time, the job will quit early without running to avoid hogging the resources.

You can refer to this official document for more details of this batch job.

Utilizing clean up jobs:

The amount of data can grow quickly over time, and some of these data might no longer be needed. Some intermediate data are used during business transactions, for example, sales or purchases orders. Once the transactions are posted, and the update history might not be needed and ready to be cleared. Each module in D365FO usually has the cleanup jobs that can be run manually or via batch to clear redundant data to free database size.

 

However, the cleanup actions of business modules affect the business data directly so your team should analyze carefully to decide what data is truly not needed before running the jobs. Usually, the jobs lie in each module Periodic/ Periodic tasks tab. A quick search of “clean up/ cleanup” keywords can show you a few examples.

Apart from the business modules cleanup jobs, one super frequent action is running batch jobs. Thus, the batch job history can pill up greatly and affect the future performance of batch jobs. It is recommended to run the batch job history cleanup regularly during off-business hours. You can check out this official document about setting up this cleanup job.

Tuning for Data Import Export jobs:

Data management tasks are common for all business. Usually, businesses have frequent imports and exports jobs. As a result, these jobs might lead to a huge amount of staging data. You should keep that in mind and regularly delete these staging data to reduce database storages as well as enhance DIXF performance. You should find the Staging cleanup feature in Data management workspace.

 

In conclusion, I hope to deliver to a few features of D365FO power that you can utilize to boost your environment’s performance. These points are a general approach to keep your overall system health under control. Depending on your business demands, you might face different scenarios, for example, some specific integration requirements, which as a result, calls for more detailed plannings and approaches of performance testing and tuning.

INET Dynamics

Microsoft Dynamics GP vs Microsoft Dynamics 365 Fin Ops: What’s the Difference?

 

Categories: Dynamics GP
Tags:

 

With the release of Microsoft Dynamics 365, there are concerns in comparing the functionality of the brand new Dynamics 365’s Finance and Operation Module with Dynamics GP Financial Management Module.

In this article, I-Net Dynamics will bring you through the differences between products in the Microsoft Dynamics product line. Specifically, we’re looking at the difference between Dynamics GP and Dynamics 365 Fin Ops, because these two offer the most common feature set and overlap, and we get the most questions to help differentiate those when organizations are trying to determine which one is best for them.

Dynamics 365 Fin Ops is Microsoft’s best-of-breed solution,built for larger  MNCs. It competes regularly with solutions such as SAP and Oracle. If your organization is a multinational manufacturer with hundreds of users, D365 Finance and Operations is a solution you should look at. It’s not for the faint of heart–implementations will take upwards of a year or longer and will require on-site, local, dedicated project management, but the solution is powerful, feature-rich and worth a look.

The D365 Fin Ops is essentially AX repurposed to be delivered via Cloud instead of installed on-premise on servers. This new version provides a Cloud-based ERP solution that can be used everywhere without the large infrastructure footprint of AX; on-premise or hosted by partners. It also has tight integration with other parts of the Dynamics 365 Family, such as CRM, so you get an end-to-end business solution containing ERP and CRM.

Dynamics GP will provide all the finance, accountant, processing, supply chain, and distribution tools that a small- or mid-size business might need.

GP gives rich functionality but is not as flexible as D365 Fin Ops. It is typically a little easier and quicker to install and maintain. Thus, if GP fits the needs of your company then it could be a little less costly and take a little less time to set up than D365 Fin Ops.

Though it is a basic accounting package, some users do not find the old-style menus and navigation options intuitive. Some features that are available in competing products are still not present in GP, such as full copy-paste functionality and more intelligent workflow/batch processing functions.

Summary

Each product has its target markets and areas of strengths.

Both Dynamics GP and Dynamics 365 Fin Ops have extremely strong core functionalities running on the Microsoft platform.

GP is intended to do more for its customers out of the box and has a large suite of add-on solutions, some of which have been around for decades.

D365 Fin Ops is built towards large scale implementations, and often requires customizations based on your business.

Ultimately, more important than the product are the capabilities of your Implementation Partner, and the consultants you will be working with.

Great GP partners can handle GP solutions for larger scale needs if required. Conversely, an unprepared D365 Fin Ops implementer would struggle with a small-scale project.

If a partner has done it successfully before, and you like what you see – you increase the chance of a successful implementation significantly.

 

INET Dynamics