The previous recipe requires an amount of preparation in order to be called, and in these cases, we would often write a facade to simplify the class's usage. They usually consist of one or more static methods for each use case that is required. Although we will have a specific use case, they are usually generic. To see examples of facade classes in standard code, type type:"class" facade into Application Explorer's search text box.
For more information on searching in SCM, please see the following links:
- Metadata search in Visual Studio: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/metadata-search-visual-studio
- Filtering Application Explorer: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/application-explorer
The facade will be specific to a target service class (in our case, the ConVMSPurchOrderGenerate class) and will be named after this class suffixed with Facade.
Facades do not have to focus on one class at a time but should focus on a topic or framework.