Articles on this Page
- 11/13/18--06:00: _GP Controller Serie...
- 11/13/18--06:15: _Building a Power Pl...
- 11/13/18--06:21: _Microsoft Dynamics ...
- 11/13/18--08:24: _Got Gaps in Dynamic...
- 11/13/18--08:31: _Show Microsoft Flow...
- 11/13/18--09:14: _CRM Systems Fail Sa...
- 11/13/18--09:43: _Air plane Headaches...
- 11/13/18--14:02: _Microsoft Dynamics ...
- 11/13/18--14:28: _Microsoft Dynamics ...
- 11/13/18--14:49: _Editing PowerBI Rep...
- 11/13/18--15:00: _Creativity at its P...
- 11/13/18--15:48: _Running Microsoft F...
- 11/13/18--22:05: _Limitations of Busi...
- 11/13/18--22:37: _SSMS: Integration S...
- 11/14/18--00:16: _Limitations of Busi...
- 11/14/18--00:19: _Power BI Desktop No...
- 11/14/18--01:14: _WPC 2018: Dynamics ...
- 11/14/18--01:21: _MB6-898 Use the Emp...
- 11/14/18--01:30: _Getting Started Wit...
- 11/14/18--01:45: _Perform Retrieve us...
- 11/13/18--06:00: GP Controller Series: Addressing Use Tax
- 11/13/18--06:15: Building a Power Platform Dream Team
- 11/13/18--06:21: Microsoft Dynamics GP 2018 R2: Start and End Dates for Pay Codes
- 11/13/18--08:24: Got Gaps in Dynamics GP Payroll? Here’s How to Fix Them
- 11/13/18--08:31: Show Microsoft Flow On Forms And In The Site Map
- 11/13/18--09:14: CRM Systems Fail Sales Teams. Can AI Help?
- Automated Data Capture: The solution should crawl your systems such as Microsoft Office 365 or Exchange, Dynamics 365 for Sales, SharePoint, Teams, LinkedIn, etc., retrieving all data related to leads, customers, prospects, and opportunities including emails, meeting details, and documents.
- Record Enrichment: New contacts should be associated with accounts and opportunities. Leads, contacts, accounts, and opportunities should be automatically enriched with all relevant data and activities.
- Analysis: Integrating AI with CRM should provide continuous analysis with vast collections of customer interactions which are organized, assessed, and scored based on dynamic, objective criteria.
- 11/13/18--09:43: Air plane Headaches, how I overcame them
- 11/13/18--14:02: Microsoft Dynamics 365 Field Services Manual Scheduling
- 11/13/18--14:28: Microsoft Dynamics 365 Field Services View Customizations
- 11/13/18--14:49: Editing PowerBI Reports in Business Central
- 11/13/18--15:00: Creativity at its Peak… Business Analysis Workshops
- 11/13/18--15:48: Running Microsoft Flow from within Dynamics 365 CE
- When a record is selected – this is the first event in the Flow and this Trigger allows the Flow to appear in the Flyout. It is connected to the Common Data Service (CDS) behind the environment it is running in. It will also prompt the user to enter in the message they want to send to the SMS recipients.
- 11/13/18--22:05: Limitations of Business Rule with Mobile App
- 11/13/18--22:37: SSMS: Integration Services Catalog node not visible
- 11/14/18--00:16: Limitations of Business Rule with Mobile App
- 11/14/18--00:19: Power BI Desktop November 2018 Feature Summary
- 11/14/18--01:21: MB6-898 Use the Employee and Manager self-service features
- 11/14/18--01:30: Getting Started With Kingswaysoft – Part Two
- 11/14/18--01:45: Perform Retrieve using Alternate Key and SDK in Dynamics 365
Use or Purchase Tax is a self-assessed tax where goods are purchases without taxes applied and the user/company is required to self-assess and remit taxes. This most often happens with inventory items that are used by the company instead of being sold to customers or with items purchased from suppliers or via jurisdictions not subject to tax. This comes up just enough and is a big enough pain, that I wanted to cover it.
Quick examples, if a grocery store takes bleach for sale of a shelf to help clean up a spill, they owe tax on that. Also, if a US company orders hard drives from a supplier in China to repair some internally used computers, the Chinese supplier has no requirement to collect and remit US tax. Instead, the buyer would be required to remit tax payments to their state.
GP has a small handful of ways to deal with use tax depending on the details, but one option stands out: Negative Tax Rates.
In GP, a Tax Schedule is a collection of Tax Details. A Tax Detail holds the specifics for a single tax rate. For example, Florida has a state sales tax rate and a different county tax rates. Each of those represents a Tax Detail. Those details get combined into a schedule and a schedule is applied to a transaction. So a 7.5% tax from a schedule might be a combination of a 6% state tax, 1% county tax, and .5% city tax.
If tax is included in an invoice, the customer pays both the invoice and the tax to the vendor. In a use tax case, the vendor gets the invoice amount and the taxing authority gets the tax amount. This is what adds a layer of complexity to the process.
GP allows Tax Details to be both positive and negative and each DETAIL can have a separate account so we can use this to create Tax Schedules for use tax. Simply create new tax details that mirror the tax rates with negative rate values. Combine both the positive and the negative rates into a single tax detail.
Now, when this rate is applied to a transaction, the net tax value on the transaction is zero, so the vendor is paid correctly. The positive rates debit an account, usually, an expense account for the tax, and the negative rates credit a liability to the taxing authority to collect those amounts all in one place.
There are some technical setup items to complete, but this is the most straightforward solution. You can find additional details in this free, Use Tax whitepaper.
Links to all the posts in this series can be found at http://mpolino.com/gp/gp-controller-series-index/
As Microsoft Practice Lead for Codec in UK and Northern Ireland, I’m regularly thinking how Codec has grown a Microsoft Dynamics practice from a small team of 2 people to over 100 Microsoft ‘Power...(read more)
With the release of Microsoft Dynamics GP 2018 R2, users can assign a 'Start Date' and/or an 'End Date' to Pay Codes in the Employee Maintenance window. This functionality is similar to...(read more)
Right out-of-the-box, Microsoft Dynamics GP Payroll offers powerful features and functionality. However, not all businesses have simple payroll processes. Over time, you may experience gaps in Dynamics GP Payroll—and we know how you can fix them.
Simple Problems Can Have Simple Fixes
When it comes to payroll, simple mistakes don’t often have simple fixes. Even the most mundane of payroll errors can take a myriad of steps to correct. Multiply these mistakes by many employees and you could easily lose an afternoon fixing payroll mistakes! Luckily, this doesn’t have to be the case. Here are three common payroll mistakes and a solution to correct them.
1. Calculating rate changes: Employees don’t often keep the same pay rate for the duration of their employment. Making a rate change should be easy, but it isn’t – especially when you make a change in the middle of a pay period. Making manual calculations is not only time consuming, but it’s prone to errors. Waiting for the next payroll run isn’t always appropriate either.
The solution: Simply make the rate change and enter the date, then let Mid Pay Period Rate Changes do the rest. Once you enter the pay rate change, the information is stored until the next payroll run. At that time, the financial change is automatically calculated, updated and processed. Employees will see two line items on the earnings statement indicating the old pay rate and hours on one line with the new pay rate and hours on another.
2. Uncontrolled overtime: Keeping tabs on overtime is another common headache in the payroll department. Uncontrolled overtime can increase payroll more than you may think. Yet setting limitations isn’t easy either. Manual calculations and complying with FLSA or other state requirements only add to the burden.
The solution: Establish your overtime rules and automate tracking with Overtime Hours Rules. Simply create the overtime rules by employee, department or position. Then, manage them by day, week, pay period or any combination of those options. Overtime is then automatically calculated with no extra steps for your payroll team. Better yet, you can establish overtime hours rules that follow FLSA and state requirements, such as the California 7th day rule. Eliminate hours of time-off tracking and calculating overtime by automating it with Overtime Hours Rules.
3. Typos, miscalculations and other basic payroll errors: It happens, everyone makes mistakes. Unfortunately, a simply payroll mistake can take upwards of 17 steps to correct. That’s not only frustrating, it’s time-consuming and time isn’t a luxury that’s always available in the payroll department.
The solution: Fix simple mistakes with a simple solution. Negative Payroll Transactions will make any payroll correction or adjustment in just one step. Simply enter a negative pay code transaction and this solution will carry the correction throughout the entire payroll process, including posting on all the core payroll reports. It really is that easy.
Fix Payroll Gaps with Simple, Affordable Add-On Solutions
While Microsoft Dynamics GP Payroll is a powerful payroll system, you may still experience gaps. Bridge the gaps by deploying add-on solutions like Mid Pay Period Rate Changes, Overtime Hours Rules, or Negative Payroll Transactions.
Do you have other gaps? Are you #PayrollAndAfraid? Not a problem! We have other solutions. Contact Integrity Data for guidance with identifying your payroll gaps and choosing the available technology that can correct those common payroll challenges.
Could you use a payroll survival kit? Then take our quick survey to tell us what you’re afraid of in your payroll department. Then we can help make sure you are Payroll and NOT Afraid!
In Dynamics 365, you can choose to show or hide Microsoft Flow on forms and in the site map from System Settings. To do this, navigate to Settings > Administration > System Settings > Customization...(read more)
CRM systems are designed to automate processes, improve customer responsiveness and increase visibility. Your teams can’t wait to get their hands on the new toolset when they think about having more accurate, secure data at their fingertips. Post-implementation, fast forward a few months and getting your salespeople to properly use your new, shiny CRM is like pulling teeth. So, what causes the disconnect?
Industry analysts generally estimate CRM project failure rates to be between 30% and 70% and user adoption – particularly seller user adoption – is the primary cause of project failure. There are thousands of articles and an entire industry dedicated to addressing this issue, and the common theme amongst them is this: the persistently high failure rates of CRM implementations demonstrate that the challenge is not easily overcome.
Why CRM Fails Sales
Process automation is foundational to CRM, which is inherently beneficial to marketing and customer service teams. Since CRM makes their jobs easier and improves the quality of their work, customer service and marketing teams are quick to embrace CRM. But for salespeople, whose focus is working with customers and driving revenue, CRM is generally perceived as a major disruption, leading to a lack of user adoption and ultimately, project failure.
Lack of Value
Theoretically, CRM systems are extremely beneficial to salespeople. Process automation provides organized and accessible customer and opportunity data, which significantly increases sales effectiveness — and formal sales process automation is proven to increase revenue. Businesses expect their CRM implementation to improve close and win ratios, in turn leading to higher commissions…another benefit for the sales team. But, unless there is obvious and rapid value for sellers in using the system and it can demonstrably improve their work experience, no amount of training, positive, or negative reinforcement is going to drive anything more than the minimal level of adoption.
Time Consuming (and boring) Data Entry
Typically, entering data in CRM is boring, time consuming, and contrary to the action-oriented nature of salespeople, which is why CRM fails to meet the expectations of businesses far too often.
Salespeople are generally reluctant and, at best, “just-in-time” data entry clerks. When demands for data exceed what sellers feel is necessary at the time, they start skipping steps and may or may not catch up to them later in the sales cycle. Many will “batch” their CRM entries daily or weekly, relying on memory or sketchy notes.
Salespeople Don’t Have All the Data
Business’ email and calendar systems are swimming with useful information about customers, opportunities and prospects. What topics are they discussing? What information are they sharing? What content are they engaging with? The holders of this information, many times, are not users of the system. Therefore, in a traditional CRM system, the salesperson would have to collect this data from other team members, manually organize it, code or assign it, and enter it into the system.
This is not a likely scenario for any individual seller and certainly not a scalable solution for any business.
How to Increase CRM User Adoption Rates
To address this issue, many businesses customize CRM systems with sales activities so that data input is part of the natural flow of the sales process. With enough investment, this strategy can work for your inside sales team. However, when it comes to outside sales or big-ticket sales, this is not a viable option.
Integrating AI and CRM
Enhancing your CRM system with artificial intelligence eliminates time consuming tasks and enables sales teams to spend more time in front of customers working on revenue generating tasks. When integrating AI and CRM, you should look for a solution, such as SalesConnect 365 that provides:
If you are interested in learning how AI and CRM can transform your customer relationships, contact our CRM consultants today.
If you are one of the few hundred people among millions who get a headache when the plane takes off and ascends to 35-40,000 feet and get even severe headaches when it starts its descent then you and I...(read more)
Hi Everyone, I am going to share information how the Field Service Manual Scheduling will work Field Service Manual Scheduling Schedule Board can be customized out of the box as you can see on the image...(read more)
Hi Everyone, I am going to discuss about the various views on the Field Service Schedule Board. Lets get's started. View Configuration Options : 1) There is one default schedule board for the organisation...(read more)
Having embed PowerBI in Business Central is well known fact, but recently in Fall ’18 release, Microsoft made it even better because now you have already added PowerBI reports on all pages where...(read more)
As a principal consultant, my favourite part of any implementation is the analysis phase. The business analysis workshops are usually conducted as one of the first activities of a project. The client doesn’t...(read more)
Wouldn’t it be great if you could trigger a Microsoft Flow from within the Microsoft Dynamics 365 CE? Well, we have been able to do that since the V9.0 release. Unfortunately there hasn’t been too much information about how to set this up and do it. If you go to the online docs and search for embed Flow in Dynamics 365 you will either get a page that shows you how to enable the Flow button for Dynamics 365 or this doc that sort of explains how to get a Flow to appear in the flyout menu within Dynamics 365.
But unfortunately, they are skimpy at best and in the case of the 2nd document listed, a little incomplete at best or a little incorrect as of the writing of this blog.
Here is the main piece of information you need to know.
Only Flows that start with the COMMON DATA SERVICE TRIGGER WHEN A RECORD IS SELECTED will appear in the Flyout. Button Flows, Recurrence Flows or Flows that start with any other trigger type will not appear in the Flyout. Additionally, as you would suspect the Flow has to be enabled before it will appear.
Note: in a future blog post I will explain how you can get around this limitation of only Flows using ‘when a record is selected’ trigger.
Now to the fun part. I will show you a Flow I put together that a user can run from within Dynamics 365.
The scenario is that you want to be able to send a broadcast Text Messages (SMS) to Contacts on a Marketing List. We will use the 3rd party service Twilio and the existing standard connector to execute this process.
Here is what the Flow looks like (if it looks a little scrunched on your screen, click on it to get a bigger view):
One of the challenges in creating this Flow is that there is a N:N relationship between the Contact entity and the Marketing List entity. And as a result we kind of have to do a double loop through the List Records Action to get the information from the List to the intermediary entity and then to the Contact.
Let’s break down each step of the Flow:
This is how the triggering event will present itself to the user. Pretty cool, Huh? Kind of like the old CRM Dialogs but not very pretty though,
2. Get Marketing List – In this action we get info about the Marketing List we selected that we will use in later actions.
3. Using a Condition Check we make sure that we have selected a Marketing List that is of a Contact Type. If not it will send a failure notification to the user. Just a little sanity check that we didn’t pick a list that is composed of Accounts or Leads. Also, note that this Flow is assuming we are working with a Static list, modifying for it to use a Dynamic list will be blogged about in a future post. FYI, Contact is a record type ‘2’.
Since the dynamic value is a little cut off, here is the full name.
4. Now here is where we start dealing with the N:N relationship and it gets a little dicey. This would be so much easier if I was just demonstrating how to send a SMS message to a selected number of Contacts in a grid view. The first List records and Apply to each is designed to get all the listmember records associated with the selected Marketing List. This is the intermediary entity relationship.
5. Now that we have the records from listmember, we need to loop through and get all the Contact Records that are connected to the listmember records.
6. Now the last step in data retrieval is to get the Contacts records themselves so that we can use attribute data from their records to send out the bulk SMS message.
7. Finally, we are ready to send out the SMS message. We will loop through each of the Contacts from the previous steps, grab their mobile phone number and send them an individual SMS.
Wrap up – There is much room for improvement in this Flow. We should set it up so that it knows who the user is that is invoking it and using a Dynamic Value for the From Phone number and in the Condition logic the recipient shouldn’t be hard coded in the TO: email field, it should also be a Dynamics Value. We ought to be trapping for Contacts that don’t have a valid mobile phone number or who might have opted out of Text Messages. Saving some stuff for a future blog post.
Originally posted on Phani Rajasekhar : One of our customer reported that couple of Business Rules are not working in Mobile app which are working perfectly in Web application. Spent so much time to understand...(read more)
Recently, while working on Azure SQL Server to execute SSIS package, we found a strange issue.
We created the Azure SQL Server from Azure Portal. We designed the SSIS package using SSDT.
To deploy...(read more)
This is very informative
One of our customer reported that couple of Business Rules are not working in Mobile app which are working perfectly in Web application. Spent so much time...(read more)
We have a massive Power BI Desktop update this month. Composite models, which allow you to combine direct query and import sources together in one model, is now generally available. Two of the top feature requests on UserVoice, expand/collapse on the ...read more
Yes… Dynamics 365 Business Central appears on the list of topics of the main Microsoft developer-oriented conference in Italy. From 27 to 29 of November, at Centro Congressi Milanofiori in Assago (MI)...(read more)
The last point in the first of the four areas, Understand the Dynamics 365 for Talent Environment (25 – 30%), is;
Use the Employee and Manager self-service features
Describe features for employee...(read more)
Now we will continue on from Part One of this series. Once you’ve indicated on the destination CRM environment that the error handling should go to an error output, you need to set where those errors...(read more)
Alternate keys have been implemented some time back and by now I think most of the consultants working with Microsoft Dynamics are familiar with the concept of alternate keys.
In case you are new to...(read more)