MB-500日本語 無料問題集「Microsoft Dynamics 365: Finance and Operations Apps Developer (MB-500日本語版)」

Explanation:

Explanation:
SQL Server Reporting Services
Controller class
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/analytics/create-nextgen-reporting- solutions

Explanation:
1. Create a runnable class and add it to the ProductUpdates project
2. Open the new class and add a main method to the class
3. Write the database manipulation code in the class
4. Set the class as startup object
5. Build and run the class

Explanation:

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/add-method-table

Explanation:

解説: (JPNTest メンバーにのみ表示されます)

Explanation:

Explanation:

Box 1: Yes
Class extension - Method wrapping and Chain of Command.
The functionality for class extension, or class augmentation, has been improved. You can now wrap logic around methods that are defined in the base class that you're augmenting. You can extend the logic of public and protected methods without having to use event handlers. When you wrap a method, you can also access public and protected methods, and variables of the base class. In this way, you can start transactions and easily manage state variables that are associated with your class.
Box 2: Yes
In the following example, the wrapper around doSomething and the required use of the next keyword create a Chain of Command (CoC) for the method. CoC is a design pattern where a request is handled by a series of receivers. The pattern supports loose coupling of the sender and the receivers
[ExtensionOf(classStr(BusinessLogic1))]
final class BusinessLogic1_Extension
{
str doSomething(int arg)
{
// Part 1
var s = next doSomething(arg + 4);
// Part 2
return s;
}
}
Box 3: Yes
Instance and static methods can be wrapped by extension classes. If a static method is the target that will be wrapped, the method in the extension must be qualified by using the static keyword.
Box 4: No
Wrapper methods must always call next.
Note: Wrapper methods in an extension class must always call next, so that the next method in the chain and, finally, the original implementation are always called. This restriction helps guarantee that every method in the chain contributes to the result.
In the current implementation of this restriction, the call to next must be in the first-level statements in the method body.
Here are some important rules:
* Calls to next can't be done conditionally inside an if statement.
* Calls to next can't be done in while, do-while, or for loop statements.
* A next statement can't be preceded by a return statement.
* Because logical expressions are optimized, calls to next can't occur in logical expressions. At runtime, the execution of the complete expression isn't guaranteed.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/extensibility/method-wrapping-coc

Explanation:
Yes, No, Yes, Yes.
https://community.dynamics.com/ax/b/nevoitechax/posts/what-is-recid-in-microsoft-dynamics-ax-365fo
Topic 3, Munson's Pickles and Preserves FarmBackground
Munson's Pickles and Preserves Farm produces and sells jarred food goods. The organization has several production and warehouse locations across the United States. Each location runs both production and warehousing operations. The company has three locations: East Central, and West.
The company is upgrading its Dynamics AX 2009 system to Dynamics 565 Finance.
Current environment
Munson s Pickles and Preserves Farm plans to migrate customizations, data, and integration from its legacy system into Dynamics 365 finance and operations apps. The Dynamics 365 finance and operations environment includes:
* multiple cloud-hosted development environments using Microsoft Visual Studio 2017
* a Microsoft Azure DevOps project for source control
* two tier 2 environments for user acceptance testing and staging, as wen as production Munson s Pickles and Preserves Farm is currently in the planning and development phase of the upgrade process- The company's internal development team needs additional development resources to address issues.
The company already created a project that rs set up to use a custom model named GPExtensions.
Integrations
Munson's Pickles and Preserves Farm has a new integration for its freight processing information. The internal development team created the secure file transfer protocol (SFTP) site for the source information to be stored and the staging table to house the source information once the data is added to Dynamics 365 Finance, information from the source will be transferred once a day from the source system and integrated with the target system. More than 10.000 records will be transferred over the integration. The company created an aggregate entity for the integration to minimize the amount of transmitted data.
Munson s Pickles and Preserves Farm has added a new integration for freight processing where all item weights, dimensions, and other factors will be configured in the external portal while planning the loads. Once the load is planned, it will be integrated into Dynamics 36S finance and operations apps for the freight invoice processing to occur.
No duplicate invoices or posting are associated with the freight invoice charges. The integration of this information from the source system is intended only for report creation and compilation purposes.
Planned changes
Munson' s Pickles and Preserves Farm wants to change inventory forms to fit its current needs. Any modifications or enhancements must follow the existing functionality for forms m Dynamics 365 Finance.
Requirements
Munson's Pickles and Preserves Farm wants to change inventory forms to fit its current needs. Any modifications or enhancements must follow the existing functionality for forms m Dynamics 365 Finance.
Integrations
All data from integrations have the same format as an existing Dynamics 365 Finance apps field. All enhancements or customizations must use existing assets before creating new functionality.
Munson's Pickles and Preserves Farm wants to change its integration strategy to include real-time data from the freight processing source system. The inventory must update as it is sold from the system. That information will be updated in Dynamics 365 Finance.
The freight processing integration requires the use of an SFTP site to store XML files from the source system.
The additional integration will use OData and must be transferred in real time.
A periodic batch job must
* Pull data from the SFTP site.
* Import the data to a staging table used to hold the information from the source system.
* Map source data to the target table m Dynamics 365 Finance.
The imported Load ID field must be added to the Sales Order header for all processed orders. Additional requirements for integrations, including other integration strategies, may be necessary as the company grows.
Existing tables must be changed to include the Load ID. The database will need to be synched before adding the Load ID field.
Changes
Munson's Pickles and Preserves Farm must change the Inventory Status form to include more columns. It plans to create a table to enter the data for the Inventory Status form as a new data source. The company wants to add both the Product Name field and Batch ID field to this new table. The current form includes the item number, location, license plate, product inventory dimensions, and quantity.
The grid on the inventory Status form must include the product name by using the item number and legal entity. The user interface must be created to include the new columns and the data must be available to add to the gnd. The form must have only an Action Pane, a Navigation List a List Style Grid, a Details Header, and a Details Tab in the design and include the Load ID field.
Munson's Pickles and Preserves Farm is currently in the process of adding the other required fields: one for Product Name and one for Batch ID- The new fields must be related to extended data types for the original fields on the existing data source for the Inventory Status form. Munson's Pickles and Preserves Farm plans to add the EcoResProductName and Batch ID data to the extended table for WHSTmpStatusChange. The fields on the table extension must be populated with data and visible on the inventory Status form on insert.
Issues
* The Internal development team has created the SFTP site connections, the staging table, and the batch Jobs for the new integration for freight processing. The development team needs to map the source data to the target table and the data management workspace. The development team notices errors with mapping target fields in the data management workspace. The team needs another developer to configure the table extensions, class extensions, and form extensions that are required for the planned changes.
* The internal development team has issues adding the required fields to the inventory Status standard form.
The team needs another developer to configure the table extensions, class extensions, and form extensions that are required for the planned changes.

Explanation:

Box 1: custom service
Custom service peak data volume is 1,000 records per hour.
Box 2: batch data API
This scenario is best implemented by using batch data APIs, which has a peak data volume of 300,000 records per hour.
Box 3: OData endpoint
Peak data volume for reading Odata status of orders is 5,000 records per hour.
This scenario is best implemented by using the OData service endpoints to read order status information.
Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/integration-overview