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.



Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

RTC Report It is not possible to instantiate the Visual Studio bridge.

Hi all, As a Navision developers I have Multiple Versions of Navision running in single Machine. As discussed Earlier in the post how to run multiple Version of RTC in single machine. So my machine have following details for RTC Versions - NAV 2009 R2    - is installed. NAV 2009 SP1  - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 SP1 IN\ NAV 2009         - is copied at C:\Program Files (x86)\Microsoft Dynamics NAV\60\NAV 6.0 IN\ This approach has been working great for execution of Classic and RTC Clients. However, after installing Dynamics NAV 2009 R2, if i tried to view the Layout for an NAV 2009 SP1 Report i was getting the following error: ---------------------------  Microsoft Dynamics NAV Classic  ---------------------------  It is not possible to instantiate  the Visual Studio bridge.  ---------------------------  OK    --------------------------- After searchi...

Dynamics NAV - All that you need to know about MenuSuites.

Hi Readers, This article is based on a request from a blog reader who wanted to understand about MenuSuite in Dynamics NAV. If you have started working with Business central with AL Code then it does not apply to those releases but if you are interested go ahead. Let's start with Future - In Latest and greatest version of product MenuSuite are obsolete and no longer used. So this article applies if you want to learn about C/AL MenuSuite.