Skip to main content

#msdyn365bc 2021 Release Wave 2 - OData callers can specify read-only intent in GET requests.

Hi Readers,

In this series we will discuss what's new in Business Central 2021 (Wave 2) a.k.a BC19.

This article we will discuss about - OData callers can specify read-only intent in GET requests.

With this series we will understand what's new the product and learn it before it becomes available for customers.

#msdyn365bc #2021RW2

Feature Details - 

Integrations that query data using OData can indicate a read-only intent to read data from a secondary database replica.

Explanation -

Till Business Central 18, we can only define read-only intent either - 

  • During API Page Creation.
  • Setting Data Intent from Database Access Intent List Page.

With Business Central 19, Data intent can also be set during call to API by specifying the Data-Access-Intent: Read-only.

While using Read-only Intent the speed of read will be faster in case of bulk reading.

  • Integrations that consume data through OData from Business Central can indicate a read-only intent to use a read-only database replica. 
  • Indicating read-only intent is done by setting a request header on the OData call.
  • This will offload read-only queries from the primary database and give more read capacity for integrations that read large amounts of data.

How to ?

Get With Read-Only

Post with Read-Only will end up an Error Message.

Error Message

Hope you learn and will be able to utilize this feature as Business Central 19 is available.  

For other articles related to What's New in Business Central 19, refer here.

Saurav Dhyani


Popular posts from this blog

Welcome - Microsoft Dynamics 365!

Hi All, In this article we will discuss the new introduced member of Dynamics Family. Yes you heard it correctly, one more new member with Name "Microsoft Dynamics 365" . #ProjectMadeira   #Dynamics365

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.