Quantcast
Channel: Microsoft Dynamics 365 Community
Viewing all 77179 articles
Browse latest View live

10 Seriously Spooky Facts About CRM’s Effectiveness to Shock Your Boss!

$
0
0

Ledgeview Partners 10 Spooky CRM Facts

Have you ever found it difficult to approach the subject of implementing a CRM system within your organization because of fear of lacking executive sponsorship?

This is a common fear users face and even suffer from post implementation when management still isn’t involved!

Certainly, we don’t want this to happen at your organization. This post walks you through some seriously spooky facts about CRM’s effectiveness in 2019 to shock your boss with.

Get them on board the CRM bandwagon this year! Pass these incredible facts along to empower your team to succeed with leading CRM technology.


1. “Social Customer Relationship Management (CRM) market worldwide is projected to grow by US $204.3 billion, guided by a compounded growth of 52.8%.” (“Social Customer Relationship Management (CRM) – Market Analysis, Trends, and Forecasts”, 2019)

2. “91% of businesses with 10 or more employees now use CRM software.” (CRM Magazine, 2019)

3. “The average return on investment a company using CRM has is $8.71 for every dollar spent.” (Nucleus Research, 2018)

4. “CRM software can increase sales conversion rates by up to 300%.” (Cloudswave, 2019)

5. “65% of companies adopt a CRM system within their first five years of business.” (Nutshell, 2019)

6.  “Effective sales organizations are 87% more likely to be consistent users of CRM or another system record.” (Nutshell, 2019)

7. “47% of CRM users said their CRM had a significant impact on customer retention and satisfaction.” (Nutshell, 2019)

8. “74% of CRM software users said their CRM gave them improved access to customer data.” (Nutshell, 2019)

9. “24% more sales reps achieve their annual sales quota with mobile access to their CRM.” (Nutshell, 2019)

10. “13% of companies say that investing in a CRM system is a top priority for their sales team in 2019.” (G2Research, 2019)


If these impressive stats still don’t convince decision-makers at your company to start the CRM research and awareness phase that comes before implementation, use our Featured Resources to guide your conversation!

Together with your executive sponsors, you can start to affect the positive change your organization is capable of, using leading technology like CRM to succeed.

Learn more about different CRM solutions your organization may benefit from here.

RESOURCES:

  • “14 CRM Stats That Sales Professionals Need to Know.” Nutshell, 17 July 2019, https://www.nutshell.com/blog/crm-stats/.
  • “14 Mind-Blowing Statistics That Prove the Need for a CRM.” Agile CRM Blog, 28 Feb. 2019, https://www.agilecrm.com/blog/statistics-that-prove-the-need-for-a-crm/.
  • ltd, Research and Markets. “Social Customer Relationship Management (CRM) – Market Analysis, Trends, and Forecasts.” Research and Markets – Market Research Reports – Welcome, 2019, https://www.researchandmarkets.com/reports/4806129/social-customer-relationship-management-crm?utm_source=BW&utm_medium=PressRelease&utm_code=6c9g62&utm_campaign=1284686+-+Global+Social+Customer+Relationship+Management+(CRM)+Market+Analysis+&+Outlook,+2019+to+2025&utm_exec=joca220prd.
  • “Nucleus Research.” Nucleus Research, 26 Sept. 2018, https://nucleusresearch.com/research/single/crm-pays-back-8-71-for-every-dollar-spent/.
  • Zangre, Andrew. “30 Noteworthy CRM Statistics in 2019.” G2, https://learn.g2.com/crm-statistics.

Contact Us Today

To learn more about Ledgeview’s Expertise

The post 10 Seriously Spooky Facts About CRM’s Effectiveness to Shock Your Boss! appeared first on Ledgeview Partners.


“Azure Functions for Dynamics 365 Business Central Developers” webcast recording

$
0
0
The recording of my last webcast for Areopa Academy is available on their YouTube channel . Again, sorry for the initial GotoMeeting problem and sorry for my error during the first demo (function deployed...(read more)

PowerApps Portals: Liquid and JavaScript – Better Together!

$
0
0
PowerApps Portals offers two primary languages for customization: JavaScript and Liquid. This leads to confusion as to which technology should be used, and when – I’ll try to clear up some of that...(read more)

Bot

Steve has another chat with Guggs

$
0
0


In this episode of “Steve has a Chat”, I catch up again with Steven Guggenheimer “Guggs” to get the latest on the ISV Connect program. I also had a few surprises for him.  Enjoy!

BTW, don’t forget, Mark Smith (@nz365guy) and I do PowerUpLive every Wednesay at 4PM EST, click here to be alerted, and here’s a link to the replays!

 

NetSuite Users: Have You Outgrown Item Commitments?

$
0
0

Facing the truth can be hard - especially when it means you will have to welcome something "new" into your life. But if there's signs you've outgrown Netsuite item commitments, it's time to face the facts. If the following apply to you, it may be time to switch to the NetSuite 2019.2 new feature Supply Allocation.

Signs you've outgrown NetSuite Item Commitments

-Do you regularly re-commit inventory to ensure sales and/or work orders can be completed?

-Do you need to consider future orders but not ALL future special orders?

-Do you need to commit items in different ways (standard orders vs replacement orders)?

-Are you manually entering transfer orders after reviewing a search?

NetSuite Supply Allocation vs Item Commitments

 

Item CommitmentsSupply Allocation
With the preference Perform Item Commitment After Transaction Entry active, NetSuite  performs automatic inventory allocation when new item quantities become available.  NetSuite will automatically remove available quantities from sales orders, work orders, and transfer orders in limited scenariosWhen you enter demand orders such as sales or transfers, the allocation engine also considers planned inventory orders, such as transfer orders and work orders, to match supply with demand based on the date that supply is required. When Supply Allocation matches demand orders that have future ship dates to supply orders with future receipt dates, on-hand inventory remains available to fill immediate demand orders.

 

Item commitments can be done manually, by order priority, by expected ship date, or by transaction date.Supply allocation calculations assess current and future inventory supply and determine the best ways to allocate supply to the demand on orders.

 

If multiple orders are changed and a large amount of inventory is removed, your setting determines which orders are affected and which orders get items allocated first. Quantities will be de-committed based on the quantity is reduced on the transaction with a committed quantity and the oldest transaction date.Create an allocation strategy to define the rules used to allocate particular inventory. You can create multiple strategies, then choose them on demand order lines to specify the way inventory is allocated to respond to that demand.  These calculations are based on the allocation strategies defined on order lines.

 

Supply Allocation is one of many enhancements NetSuite offers to make your Supply Chain seamless. To learn more ways NetSuite can enhance supply chain - and your business - send an email to our NetSuite experts.

Manage configuration data with Dynamics 365 Finance and Supply Chain Management

$
0
0
For every implementation, configuration data is managed. At times we move configuration data between instances and sometimes just copy to another legal entity in same instance. Read blogpost below to ...(read more)

Key Concepts for Microsoft Dynamics 365: Entities and Attributes

$
0
0
Types of Dynamics Entities To understand Microsoft Dynamics 365 (formerly Dynamics CRM and Dynamics 365 Customer Engagement), you need to learn some new terms and concepts that may be a bit different...(read more)

Environment Variables preview

$
0
0
A number of folks have pointed out that solution environment variables are, now, in preview: https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/environmentvariables I was looking...(read more)

What is IRS Letter 5699?

$
0
0

Employers have been tasked with complying with the Affordable Care Act (ACA), but many have bought into the notion that it won’t be enforced or it will be repealed before any enforcement actions begin. IRS Letter 5699 gives the employer choices on how to respond regarding their filing situation. The letter asks the employer if they:

  • Filed the forms under a different EIN. (They are asked to provide the name, EIN and date for when the returns were filed).
  • Should have filed the forms, but did not. (They are asked to either submit the delinquent forms with the response, or provide an explanation of when the returns will be electronically submitted).
  • Were not an ALE, and thus not required to file.
  • Had an "Other" reason to not file.

These letters have been going out to employers whom the IRS identifies as potential non-filers of the required ACA Information Returns (Form 1094-C and 1095-C). On the June 6, 2019 IRS Payroll Industry call, the IRS identified that for the 2016 tax year, 8,194 letters were mailed to employers. This went up to 8,752 letters for tax year 2017. Those letters were to be sent between May 15, 2019 and July of 2019.

Even if an employer complies with the requirement to offer compliant coverage to required individuals, failure to file the required forms will result in penalty. For 2019, that’s $540 per eligible employee. Read more about IRS enforcement of the ACA here.

Have you received a IRS Letter 5699 and need help moving forward? Contact us and we’ll be happy to assist. Also, please visit acafluent.com to get up to speed on all things ACA.

Written by Integrity Data

"Custom plug-ins should not catch exceptions"... that's new.

$
0
0
The title refers to an error message I got today in one of my plugins, the complete text is the following:

ISV code reduced the open transaction count. Custom plug-ins should not catch exceptions from OrganizationService calls and continue processing.

I googled the message and I found the explanation inside the following page: Troubleshoot plug-ins.
The reason is simple: inside my code I wrapped an IOrganizationService.Update inside a try catch block:

try
{
Entity updateRecord = new Entity(recordRef.LogicalName, recordRef.Id);
updateRecord[fieldName] = fieldValue;
service.Update(updateRecord);
}
catch (Exception ex) {
// ...
}
Why I did that? In my case the specific update may or may not fail (due to the status of the entity and the field that I need to update) but I needed to make sure the plugin containing the above code should never fail.
I don't have a specific workaround to resolve this situation because it really depends on the logic you have inside the plugin (in my case one of the options is to create an additional async plugin just to perform this update so it will not affect the main plugin).
The page mentions that this error has been added recently, so if in your existing plugins you have an IOrganizationService call wrapped inside a try catch block, the plugin is probably failing right now.

Hope it helps

Pushing, Dragging or Pulling an Industry Forward

$
0
0
Quite a few years ago, in my previous job when I was an MVP still, I did an online webinar for the AXUG called "Putting Software Engineering back in Dynamics AX" (in 2014). Admittedly it was somewhat of a rant / soap box type of talk. I guess "food for thought" would be a more optimistic characterization. I did try to inject some humor into the otherwise ranty slides by adding some graphics. At the time we were building out our X++ development team and we were heavily vested in TFS and automation, and I was very keen on sharing our lightbulb moments and those "why did we only start doing this now" revelations.

Fast forward 5 years to a new generation of technology and a shift to cloud. In fairness, many more people are engaged in some of these topics now because the product finally has features out of the box to do builds, use source control without tons of headaches and setup, etc. But contrary to the advice on one of the original slides from 2014 that said "Bring software engineering into AX, not the opposite" - it sort of feels that is exactly what has happened. People projecting their AX processes onto some software engineering processes. Sometimes ending up with procedures and technology for the sake of it, and not actually solving any problems at all and sometimes even creating more problems. But, they can say they ticked another checkbox on the list. I have stories of customers with messed up code in production, because someone setup branching because they were told that's a good thing to have. Yet nobody knew what that meant or how to use it. So code was being checked into branches left and right, merged in whichever direction. Chaos. A perfect example of implementing something without having a good reason or understanding to do so. On the flipside, we have customers calling us up because they "redeployed" their dev VM, and want to know how they can get a clean copy of their code from production back into their VM. Now, part of that is legacy thinking and not understanding the technology change. But honestly that was never a good thing in older versions either.

Anyway, that brings us to my topic du jour. As you may or may not have heard and read, we're working on elevating the developers tools further. We'll become more standard Visual Studio, standard Azure DevOps. This is all great news as it will allow X++ developers to use more of the existing tools out there that can be used for any standardized .NET languages or tools. The problem is not that we'll be forcing people to use advanced tools they don't know how to use. They can still choose to not use source control or build automation. I'm more worried about the people using all these new tools and not understanding them. What if in the future we start supporting Git? Will our support team be overwhelmed with people stuck on branching, merging, PRs, rebasing and all the great but complex features of decentralized source control? We've never dealt with situations where we "support" the technology (i.e. the tools are compatible) but we won't support the user of that technology (sorry your production code got messed up, go get some training on Git branching and good luck to you on recovering your production environment). In the history of our product, we've never drawn a big line between technical compatibility but not supporting the usage of it. But we will have to. How about other areas, like PowerBI, PowerApps, etc.? Yes they are supported and will be integrated further, but will Dynamics 365 support answer your usage questions?

I've had frank discussions with developers (that I personally know), where I basically tell them "the fact you're asking me these questions tells me you shouldn't be doing this". But that's not an attitude we can broadly apply to our customer base.

So I ask YOU, dear audience. Where and how can we draw a line of supportability?

Microsoft’s Modern Lifecycle Policy, What Does It Mean For Me?

$
0
0

As you might have heard, Microsoft released a brand-new version of Microsoft Dynamics GP earlier this month. As with all GP releases, it brought with it a ton of great features, a few favorites of which we showcased in a recent post on our company blog. Interested? Check it out here. But new features were not the only big change to come with this version of Dynamics GP. With this release, Microsoft also moved Dynamics GP from a traditional fixed lifecycle policy to their modern lifecycle policy, which governs the updates for Office 365 and many of the software giant’s newer products/services.

 

What does this shift mean for me?

Microsoft’s move to add Dynamics GP to its modern lifecycle policy is good news for Dynamics GP users. It solidifies Microsoft’s commitment to maintaining GP with at least three regular updates each year for the foreseeable future. So, if you’re a fan of Dynamics GP and were afraid you’d have to leave your beloved accounting software behind sooner than you would like, fear not.

Also, instead of only getting a big release with new features every other year or so, which had long been the case with Dynamics GP, users can look forward to receiving updates more often.

 

Under the modern lifecycle policy, the yearly update schedule looks like this:

  • June/July – security and regulatory updates
  • October – large update with customer requested new features
  • November/December – year end updates

 

Plus, GP developers will release additional security updates, quality fixes and hot fixes throughout the year, as needed.

 

With this faster release cadence, you may wonder how long Microsoft plans to support each new release. That’s a great question. Unlike the traditional fixed lifecycle, under the modern lifecycle, releases no longer have expiration dates. Mainstream and extended support are a thing of the past. Instead, as long as you “stay current” Microsoft will continue to support your software until it announces the end of the product (which there is no announced plan to do).

What does it mean to “stay current?”

This is a new term to the Dynamics GP vocabulary, and one that can seem confusing at first. But it’s simple. To “stay current” all you have to do is apply at least one update per year. For example, if you want to have access to the 2021 releases of Dynamics GP, you will need to install either the June/July, October, or November/December released in 2020.

 

When will my company make the switch to the modern lifecycle policy?

The answer to this question depends on what version you are on now and how long you take to move to the latest release. GP versions released prior to this October remain on the traditional fixed lifecycle. Once you upgrade to the October 2019 release or a subsequent one, you will move to the modern lifecycle policy.

 

I still have questions. Where can I get more information on the modern lifecycle policy and how it compares to the fixed one?

That’s understandable. That’s why we put together a brief fact sheet comparing the two policies and answering some of the most common questions GP customers like you have about the switch.

 

Download your copy now.

Ready to take advantage of all the October 2019 release of Dynamics GP offers? Contact us to begin your upgrade.

 

New Series #TGIF, Thank God It’s Flow

$
0
0
Hi Readers and Viewers Thanks for your support! As promised, I am coming up with a new series #TGIF. It… (read more)

Export model from modelstore of Microsoft Dynamics 365 Finance and Operations one version

$
0
0
While DevOps exists, still those who would like to take an additional backup of your effort, sharing a quick step to to Export model from modelstore of Microsoft Dynamics 365 Finance an...(read more)

Planning as a service in Microsoft Dynamics 365 Finance and Operations one version

$
0
0
Quick intro to Planning as a service in Microsoft Dynamics 365 Finance and Operations one version Currently in preview (private and soon public preview in Nov 2019) 1) Install planning optim...(read more)

Microsoft Dynamics CRM Online 2016 Update 1 New Features- CRM App for Outlook

$
0
0
www.youtube.com/watchThis training will cover the new features in Microsoft Dynamics CRM Online 2016 Update 1 / CRM 2016 Service Pack 1 for the CRM App for Outlook. This training will cover the following: Requirements New Features Demo Configuration/Deployment Components Architecture Troubleshooting Known Issues Additional Documentation https://community.dynamics.com/crm

Microsoft Dynamics CRM Online 2016 Update 1 New Features- Power BI

$
0
0
www.youtube.com/watchThis training will cover the Power BI side with an overview and demonstration of capabilities. This training will also cover the CRM side and new features of Power BI in CRM. Topics include in the course include: Power BI introduction and overview Demonstration Requirements New Features Provisioning User Dashboard Components Architecture Troubleshooting & Known issues Tools and Resources https://community.dynamics.com/crm

The Microsoft Dynamics Modern Store - Fashion Retail

$
0
0
www.youtube.com/watchSarah is a shopper in the Generation Y/Z demographic. She likes to be connected at all time, and opts in to share her location and to receive notifications. This video shows how Microsoft solutions based on Microsoft Dynamics can help the retailer to engage their customer consistently, enjoyably, and profitably. Products facilitating this scenario are: Microsoft Dynamics AX, Dynamics CRM, Dynamics Marketing, Dynamics Partner Solutions, Dynamics AX Modern Point of Sale, and Microsoft Social Engagement. To learn more about Microsoft Dynamics click here: https://www.microsoft.com/en-gb/dynamics/retail.aspx

The Microsoft Dynamics Modern Store - Electronics Retail

$
0
0
www.youtube.com/watchGreg is a shopper in the Generation Y demographic - he likes to be connected, but only when he decides to. This video shows how Microsoft solutions based on Microsoft Dynamics can help the retailer to engage their customer consistently, enjoyably, and profitably. Products facilitating this scenario are: Microsoft Dynamics AX, Dynamics CRM, Dynamics Marketing, Dynamics Partner Solutions, Dynamics AX Modern Point of Sale, and Microsoft Social Engagement. To learn more about Microsoft Dynamics click here: https://www.microsoft.com/en-gb/dynamics/retail.aspx
Viewing all 77179 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>