From the Microsoft Dynamics 365 Finance and Operations Blogs: Revenue recognition; Environment update; Build automation; Enhancing security

In this week's Microsoft Dynamics 365 Finance and Operations blog roundup:

• Harnessing the power of Microsoft Dynamics 365 Finance’s revenue recognition tools in the pharmaceuticals industry
• Apply environment update to D365FO via command line
• D365FO: build automation using Azure pipeline and Microsoft-hosted agent
• Enhancing security: Microsoft Sentinel solution for Dynamics 365 Finance and Operations

Harnessing the Power of Microsoft Dynamics 365 Finance’s revenue recognition tools in the pharmaceuticals industry

Writing on the Logan Consulting blog, Fred Liu stated that because of its intricate revenue structures, managing revenue in the pharmaceutical industry requires accuracy and precision.

Liu noted that to manage revenue effectively means successfully breaking down multi-element orders so that revenue can be recognized based on company-specific and industry-specific guidelines. He stated that Dynamics 365 Finance’s revenue recognition tools can streamline this process.

It’s important to note that revenue recognition, including bundle functionality, isn’t supported for use in commerce channels like e-commerce, POS, or call center. Therefore, items configured with revenue recognition should not be added to orders or transactions created in these channels.

In his blog post, Liu described how to optimize the revenue recognition processes and perform such tasks as allocating and deferring revenue. He also offered information about the benefits of effective revenue recognition.

Apply environment update to D365FO via command line

On his blog, Microsoft MVP Alex Meyer explained in detail how users can update their environments when Microsoft releases newer versions.

He stated that the first step is to download and update deployable package from Lifecyle Services by going to the shared asset library, then navigating to the software deployable package, downloading the deployable package update, opening a command prompt (with administrator privileges) and navigating to the folder where the update package resides.

Meyer stated that after these commands are executed, the installation process, which could take up to several hours, will begin.

Meyer noted:

Once the installation has completed, I always recommend restarting the development environment. Once completed we can check the version information to confirm that the environment has indeed successfully updated.

Build automation using Azure pipelines and Microsoft-hosted agent

Writing on the Encore Business Solutions blog, Henry Villanueva stated that his blog would guide users through automating the build release using Azure pipeline and Microsoft-hosted agents. He noted that to create a build release, users must set up a cloud-hosted build environment in Lifecycle Services (LCS), which is a virtual machine in Azure that costs users money depending on the size of the machine and how long they use it.