Microsoft Dynamics 365 F&O

Dynamics Community 101 is a blog dedicated to share insights on Microsoft Dynamics 365 Finance and Operations, Microsoft Azure, and Microsoft Power Automate. Authored by Atul Yadav(Me), a Microsoft Dynamics 365 F&O Technical consultant, this blog offers in-depth articles, tutorials, and best practices to help professionals navigate the complexities of Microsoft platforms. From customization tips to integration, Dynamics Community 101 serves as a valuable resource for those looking to enhance their knowledge and skills. If you want to stay updated with the latest trends and advancements of Microsoft Technologies keep visiting Dynamics Community 101. So all in all Expert Insights on Dynamics 365 FO, Azure DevOps, LCS and Power Platform on Dynamics Community 101 by Atul Yadav.

What's new or changed in Microsoft Dynamics 365 F&O

To see what's new or changed in each and every release of Microsoft Dynamics 365 Finance, see. Link

What's new or changed in Platform updates of Microsoft Dynamics 365 F&O

As of February 19, 2024, the maximum number of consecutive updates that can be paused is being reduced from three to one. However, because release durations are being extended, the same minimum of two service updates per year is maintained.

To enable the new release cadence to be introduced with the first 2024 service update, some release milestones for 10.0.38 were adjusted. More

Copilot in Microsoft Dynamics 365 F&O

Copilot gives users access to AI capabilities that augment the application experiences and functionality of finance and operations apps. Copilot brings a growing set of skills that help users complete various tasks. It can appear in many different user experiences. More

Explore the ecosystem and main components of finance and operations apps

Explore the Dynamics 365 ecosystem. Here

Find Microsoft Dynamics 365 Partner

Access an industry-leading Microsoft partner ecosystem that offers expert guidance and support in buying, implementing, and optimizing your Dynamics 365 applications. More

Pricing for Microsoft Dynamics 365 F&O

Understanding the pricing structure of Microsoft Dynamics 365 licenses is crucial for organizations planning to implement this powerful ERP solution. Microsoft offers a flexible licensing model tailored to meet various business needs, ensuring scalability and cost-effectiveness. The licenses are available on a per-user, per-month basis, with different plans catering to diverse functionalities such as Finance, Supply Chain, and Human Resources. By selecting the appropriate license type, businesses can optimize their investment and leverage the full potential of Dynamics 365. More

Top blogs of Dynamics 365 FO and Azure

Dynamics community 101

Using the 'Like' and 'Not Like' Operators in Dynamics 365 F&O for Efficient Data Filtering

The `like` and `not like` operators in Dynamics 365 Finance and Operations provide powerful querying capabilities for pattern matching within data fields. The `like` operator allows for the selection of records that match a specified pattern, as demonstrated in the `LSSelectClaimRecordsWithIn` class, which retrieves claim records starting with "in". Conversely, the `not like` operator enables the exclusion of records matching a pattern, as shown in the `SelectClaimRecordsNotStartingWithIn` class, which selects claim records that do not start with "In". These operators are instrumental in filtering and retrieving relevant data from large datasets efficiently. Proper utilization of these operators can significantly enhance data querying and reporting capabilities within the ERP system.

Like operator :

class LSSelectClaimRecordsWithIn extends RunBase

{

public static void main(Args _args)

{

SelectClaimRecordsWith obj = new SelectClaimRecordsWith();

obj.run();

}

public void run()

{

ClaimTable claimTable;

select * from claimTable

where claimTable.ClaimNumber like 'in%';

while (select * from claimTable

where claimTable.ClaimNumber like 'in%')

{

info(strFmt("ClaimNumber: %1, ClaimDate: %2, ClaimAmount: %3",

claimTable.ClaimNumber,

claimTable.ClaimDate,

claimTable.ClaimAmount));

}

Not Like operator :

class SelectClaimRecordsNotStartingWithIn extends RunBase

{