Cached web services calls
in this section you can find a nice post by NAV Team blog about “cached web services calls”:
In a service-oriented deployment, web services are used to extend NAV’s functionality and reach. Depending on how volatile this data is and the corresponding usage scheme, it is expected to be up-to-date within a pre-defined period of time (e.g. once a day).
When NAV is integrated with external services, then the user scenarios become dependent on the data and functions offered by such services. Eventually, there are different approaches through which the external data can be retrieved, stored and used.
- Dynamic: either exposed by the external service itself or by a separate catalog that NAV can query.
- Advantage: data is always up-to-date
- Disadvantage: it requires constant connection to the data source.
- Static: hard-coded in the database for the user to benefit from.
- Advantage: data is promptly available when needed.
- Disadvantage: if data changes at some point, it will require a maintenance effort, which exposes the business process to a risk of failure.
- Cached: offered through an external service and gets pulled according to a pre-defined refresh rate or manually.
- Advantage: data is ‘up-to-date’ within the rules acceptable by the business process, without extra load on the network resources or the external service.
- Disadvantage: if data changes while the auto-refresh did not happen yet, the user may not have access to the latest data; however, the user can manually force a refresh of the data, if asked to do so.
When to Use It
Offer data in lookups that were cached from an external service.
Source with samples: Cached Web Service Calls – Microsoft Dynamics NAV Community
Design Patterns Wiki
Read the “wiki page” on the Microsoft Dynamics Community!