MB-500 — frequently asked questions

ATL is built on exactly these two concepts: navigation objects reach entities and business logic, while creator classes set up test data. Together they let you write repeatable acceptance tests against native finance and operations functionality.

No. The Microsoft ATL documentation describes navigation objects and creator classes as the library's core concepts, so no additional framework is required beyond creating that class set in a development environment.

Building a project compiles code and report definitions and produces artifacts, but it does not publish the report to the SSRS server. Deployment is a separate Deploy Reports command run from Application Explorer or Solution Explorer.

No. Build Models only controls whether reports are compiled during a build; as the community clarified, you can check 'build reports' there, not 'deploy reports', so building remains a prerequisite rather than a deployment action.

'Add files to source control' puts a brand-new, untracked file into the repository. 'Check out for edit' marks an element that is already in version control as editable so your modification can later be checked in.

In the Team Explorer window of Visual Studio, open Pending Changes, review the modified elements, add a comment, and select Check In to commit them to Azure DevOps version control.

Enums in Dataverse virtual tables typically create two columns (value and label), which violates the requirement for the same total number of fields.

No, Container types are generally not supported as direct columns in standard virtual table schemas for simple 1:1 mapping.

A recurring export runs on a schedule, so it only delivers data periodically and cannot signal the exact moment purchase order data changes. A data event fires immediately on the CRUD operation.

Data events are a category of business events raised automatically by CRUD operations on data entities. Other business events are emitted by application code, whereas data events require no X++ and are configured on the entity itself.

BYOD (bring your own database) exports data entity records to an external SQL database for analytics and warehousing. It is a one-way outbound path and never loads data back into finance and operations.

No. Entity store holds aggregated entity data in an analytical data lake for Power BI and embedded reports. It supports reporting consumption, not inbound data migration.

On the exam it counts as a complete solution for smaller reference data exposed as a public data entity via OData. In production, prefer a Data Management import job for volume, but Excel is still a valid loading mechanism.

Chain of Command for tables uses Table Extensions, not generic classes, to ensure proper inheritance and method overriding capabilities.

No, standard Microsoft tables are locked. You must create an extension in your custom project to modify or extend their behavior.

The Designer edits a specific ER configuration record; without a registered data model configuration such as Payments (simplified model), there is no artifact to open, no draft version to generate, and no structure to edit.

Yes. Both steps edit the same open designer draft — adding a Party record with a Name field and an Agent record for the bank — so either relative order is accepted as long as configuration creation and the Designer draft come first.

You either fail to open a Designer at all or edit a version that cannot be validated and completed, which breaks downstream format mappings that expect Party and Agent nodes for the banking output.