Power BI 101 Series: Sales Reporting Dashboard with Power BI Webinar
In the third part of our webinar series, we’ll be demonstrating how to build a Power BI sales reporting summary from scratch. The sales dashboard will provide not only an overview of your business’s sales performance but also make it easier to drill into sales performance analytics. You will learn all the steps needed to connect your sales data from within Microsoft Dynamics and transfer it into Power BI. Watch us step-by-step as we show you all the calculations needed to make a sales reporting dashboard. By the end of this webinar, we'll show you how to create the following:
1.Sales by Product Line
2.Customer by Location
3.Sales by Customers
4. Top Salespersons
Date: Wednesday November 14, 2018
Time: 2:00PM-3:00PM EST
Did you know that there is an auditing feature which comes standard out of the box with Microsoft Dynamics 365? All you need to do is enable and configure it to your needs and going forward all enabled actions will be logged. Auditing allows organizations to easily track high level record changes, granular field level changes, and user log in within the system.
By default, auditing is not turned on in Dynamics 365, so if you are interested in this feature you will need to enable and configure your auditing preferences. D365 provides the flexibility to enable/disable auditing at the organization, entity and attribute levels. It is worth mentioning that to audit at the field level, auditing must be enabled for the organization and the entity.
Enable auditing at the organization level
1. Auditing setup is under the Settings Tile. Click on Auditing and go to Global Audit Settings. To enable auditing, if not ticked already, tick the box Start Auditing.
2. After either ticking the box to start auditing or confirming it is ticked, you will then need to choose specific entity categories that you want to enable auditing for. In this step, you are simply defining the entity clusters, you will still need to enable auditing for each entity you want to audit within the grouping. Do note that as you hover over each group, a tooltip appears which defines the included entities.
Enable auditing at the entity level
To enable auditing at the entity level, go to Settings > Customizations > Customize the System. Expand the Entities tab and select the entity that you want to turn on auditing for.
The Auditing checkbox is unchecked by default for all entities, once checked, you will be prompted that all fields in the entity are enabled for auditing. If you don’t want a field to be audited, you can either disable auditing on a field-by-field basis or mass select fields and edit their audit setting (enabled or disabled).
Check auditing history
Audit history is stored under each record, you can simply open a record in Dynamics 365 and click on the drop down beside the record on the top navigation bar. You will be presented with an “Audit History” where you can view all audited data changes.
You can also access a summary of all audited data by navigating to Settings > Auditing > Audit Summary View.
The ability to retrieve and display the audit history is restricted to users who have certain security privileges: View Audit History and View Audit Summary. There are also privileges specific to partitions: View Audit Partitions and Delete Audit Partitions.
The following list identifies the data and operations that can be audited:
- Create, update, and delete operations on records
- Changes to the shared privileges of a record
- N:N association or disassociation of records
- Changes to security roles
- Audit changes at the entity, attribute, and organization level. For example, enabling audit on an entity
- Deletion of audit logs
- When (date/time) a user accesses Microsoft Dynamics 365, for how long, and from what client
What if your most depended upon customer service rep leaves the company and no one else on the team has the level of knowledge he had on various topics? Or at the most granular level, wouldn’t it be incredibly useful if canned suggestions surfaced when opening a service case for a customer?
There is no reason to spend excess time and money researching and troubleshooting the same (or similar) issues repeatedly. Plan ahead and build a knowledge base which withstands the test of time (and turnover) and is shareable both internally and externally.
Knowledge Articles in Microsoft Dynamics 365 provide the ability to create articles with versioning and translation functions. Building a base of Knowledge Articles allows Customer Service Reps to reference and utilize the information to deliver accurate and consistent information to customers, while following the organization’s processes.
By providing access to the article directly from a Case record, the rep can link the article to the case, thereby documenting its inclusion as a step for resolution. Not only can the rep use the information as an assist to themselves, they can opt to share the article with their customer, who may prefer to “do it themselves.”
Knowledge Articles not only benefit reps, who now have answers at their fingertips, those that administer the articles also have something to gain. Analytics are measured which provide article insights for content managers. A couple key stats are how many views each knowledge article has, and the Cases which have been associated to the article. These statistics allow administrators to not only evaluate which articles provide the most value, but ultimately it may provide intel into where there may be a bigger issue which needs attention.
It is worth mentioning that the topic discussed herein is an updated feature which has gone through a handful of iterations throughout the years with Microsoft Dynamics CRM. This most current version introduces some major improvements and enhancements over previous iterations. Do note, that while you can continue to use the legacy Knowledge Base Articles, it is good practice, and a Microsoft recommendation, to transition to the Dynamics 365 Knowledge Articles, as they provide improved capabilities and translation support. Microsoft has confirmed that the legacy Knowledge Base Articles will be deprecated sometime in the near future.
Ever wonder how your team can work more efficiently in D365? The answer is automation, and the number one tool to automate processes in D365 is workflows. Many of the simple (and complex) tasks users perform in D365 can be automated using workflows. Workflows evaluate given parameters and perform actions based on predetermined logic. Such an example is the automation of sending a welcome email when a new contact is created without you having to lift a finger.
Workflows in D365 are processes that typically work in the background to automate the flow of information. D365 Workflows are comprised of triggers, conditions, steps and actions. These properties determine the behavior which you want to have occur which impact your D365 records.
There are many functions you can accomplish using workflows in D365, below are some of the most common:
- Automate Emails – Send out Emails to accounts, contacts or users when a certain criterion is met
- Transfer Information – Automatically pass data from one entity to another entity
- Update Fields – Update fields value based on different conditions and field value changes
Join us for the second part of the Power BI 101 series as we drill into how to create a financial dashboard. Displaying financial data on a single dashboard allows you to monitor and optimize any financial trends. In just a few clicks we’ll show you how to create a dashboard using your own financial data.
- View all of your financial data on a single dashboard
- Drill down into specific metrics that are important to your business
- Monitor finances to help with future forecasting
Date: Tuesday October 30, 2018
Time: 11:00AM - 12:00PM EST
Dynamics 365 Business Rules help organizations achieve automation by performing tasks for users based on predetermined logic. This means less time entering data and more time making key decisions. Business Rules can also be used to enforce behavior by controlling certain field properties. This allows upper management to ensure proper steps are taken daily. If these controls are implemented properly, both the organization and users will see the benefit afforded through the configuration of Business Rules.
Business Rules in Dynamics 365 are a simple way to apply logic to your business data without the need for any code. D365 Business Rules are effective, yet easy to manage. The typical Business Rule follows the “if, then” statement structure and often contains two or more parts. The first part is always a condition statement where you state the condition which will trigger the business rule to take effect. The second part is the action, meaning once the set condition has been met, what action should be performed.
Below is sample Business Rule diagram to illustrate how a typical Business Rule is setup.
As you can see, the condition statement is checking the Estimated Revenue for an opportunity, if the Estimated Revenue exceeds a certain threshold then an account manager must be associated to the opportunity. Simple rules like these can help organizations improve their daily process and grow more effective to achieve their goals.
Business Rules in Dynamics 365 can perform an explicit set of functions against records. Below is a list of the actions and what each does.
- Create Business Recommendations: Provide users a recommendation on suggested next action
- Lock/ Unlock Fields: Lock/Unlock fields to control user input
- Show Error Message: Alert users when certain key information is missing or entered incorrectly
- Set Field Values: Automatically populate fields based on set conditions
- Set Default Value: Enter default value on normal conditions
- Set Field Requirement Levels: Enforce data capture to ensure fields are completed
- Set Visibility: Show and hide fields based on conditions
Now that you know what Business Rules are capable of, why not try creating one for yourself. Checkout our step by step instructional video on how you can setup your own business rules.
Management Reporter provides the flexibility of consolidating financial data across one or multiple organizations in one single report. This report includes a summary (consolidated) report for all companies as well as the option to view a report for each of the companies that you are using on the consolidation.
The simplest method to create a consolidation of all companies is by using a reporting tree. A reporting tree is an optional “building block” that allows you to list all companies to be consolidated. Once the report is generated you will have the option to select any company from the reporting node on the consolidated report.
Viewing Companies Side by Side
The second option for consolidated reports is to show each company side by side. This can also be achieved by defining a reporting tree with all companies and using that reporting tree to assign each company on separate columns.
Consolidated currency translation
Management Reporter also offers the ability to consolidate different currencies in on the report, where users can select at real-time any currency previously setup in each Dynamics GP company. The following items must be set up to achieve currency translation: