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

"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.

UPDATE: looks like that wrapping an IOrganizationService call was never possible, but the platform before returned a non meaningful error message (like "no active transaction found"), at least now we are notified with the exact reason. Thanks Tanguy Touzard and Jonas Rapp for the correction!


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)

How Do I: Configure the Outlook Add in for Microsoft Dynamics NAV 2017?

$
0
0
www.youtube.com/watchThis video demonstration covers the following steps: - the neccessary prerequisites to configure the Outlook Add-in - setup - usage Learn more at http://aka.ms/NAVGetReady or send an e-mail to kschimke@microsoft.com

Dynamics 365 Marketing | 2019 release wave 2 overview

Lägga till användare i CRM Online

$
0
0
www.youtube.com/watchBehöver du lägga till användare i Microsoft Dynamics CRM Online, men vet inte var du ska börja? Titta på det här videoklippet så får du lära dig allt du behöver veta. Du får se var du börjar i CRM, hur du anger de obligatoriska användaruppgifterna och sedan ser till att alla har en CRM-säkerhetsroll. Du får också lära dig dela inloggningsuppgifterna med dina användare så att de vet hur de ska logga in på CRM Online.

Dynamics 365 - Installing Field Service in Customer Engagement


Dynamics 365 - Installing Field Service Power BI Reporting Suite

Bring out the best in your people | Microsoft Dynamics 365 for Talent

Intelligent Supply Chain with Microsoft Dynamics 365

Dynamics 365 for Retail - Features Overview

Dynamics 365 for Retail - Overview

Dynamics 365 for Retail | Business Applications Spring 2018 Release

Seamless Commerce & Omni Channel Excellence with Microsoft Dynamics 365


ArcherPoint Dynamics NAV Developer Digest - vol 265

$
0
0

ArcherPoint Dynamics NAV / Business Central Developer Digest - vol 265ArcherPoint's Developer Digest Weekly Blog

The NAV community, including the ArcherPoint technical staff, is made up of developers, project managers, and consultants who are constantly communicating, with the common goal of  sharing helpful information with one another to help customers be more successful.

As they run into issues and questions, find the answers, and make new discoveries, they post them on blogs, forums, social media...so everyone can benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this community—so we thought, wouldn’t it be great to share this great information with everyone who might not have the time to check out the multitude of resources out there? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from NAV experts and devotees around the world. We hope these insights will benefit you, too.

D365 Business Central Release Schedule and Product Lifecycle

Saurav Dhyani informs us of the new product release cycle and naming from Microsoft for D365 Business Central. As they did this year, there will be two releases – one in the first quarter of every year, called “Wave 1” and one in the fourth quarter of every year, called “Wave 2”.

Additionally, in his post Dynamics NAV and Business Central – When Will My Version Be Out of Support?, he gives the Microsoft dates for end of support for Dynamics NAV 2015 through D365BC 15.x.

Setting Up a Database in D365BC 2019 Wave 2

Saurav continues his education in this post, instructing how to setup a new database in the most recent Dynamics 365 Business Central release, Wave 2 of 2019. You’ll need some free time and PowerShell to follow the steps.

He also notes that a PowerShell cmdlet is required to create a new database during an on-premises implementation of Business Central 2019 Wave 2 with base extensions.

You may also find his post on the steps for a new implementation on this same release helpful.

How to Upgrade Data from C/AL to AL Tables in D365BC 2019 Wave 2

Continuing on with education on the most recent release, Syed Aley Mehdi shares How to Upgrade Data from C/AL to AL Tables.

Remote Development for Business Central with VS Code

Tobias Fenster, via tech blog, shares what he learned at Directions EMEA regarding the move from C/AL to AL. Microsoft has introduced VS Code Remote Development Extension Pack, which should help alleviate the resource constraints you may be facing. He’s also optimistic about the future tools to help with remote development.

 

If you are interested in Dynamics NAV and Business Central development, be sure to see our collection of NAV/BC Development Blogs.

Read the "How To" blogs from ArcherPoint for practical advice on using Microsoft Dynamics NAV and Dynamics 365 Business Central.

Blog Tags: 

Calculate totals of RFQ reply using X++ in D365FO

$
0
0
It is often difficult to calculate the totals of RFQ reply using X++ in  D365FO . The form of Totals in Manage replies form show Totals of RFQ reply , but it is difficult for developers to get them...(read more)

Auto Capturing Emails In Dynamics 365 CRM

$
0
0
Introduction If you are looking to keep your email messages private then here is the latest feature of Dynamics 365 CRM – ‘Auto Capture’ by which you can view and keep your email message private against...(read more)

Inject PowerApps Environment Variables into Entity Record Data

$
0
0
PowerApps Environment Variables, a new solution component that provides a great way to transport a definition, default value and override value used in configuration. This provides a lot of opportunity...(read more)

New Dynamics 365 Logos

$
0
0
Recently Microsoft announced new rebranded BusinessApps icons. I wanted to show you all those new logos on one place. There are all 28 Microsoft BusinessApps icons… YES, we have 28 apps in Microsoft BusinessApps...(read more)
Viewing all 52151 articles
Browse latest View live


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