MB-500 flashcards
MB-500 · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Model versus package
- A model is a group of AOT elements that compiles together and can reference other models. A package is the deployable unit and may contain one or more models.
- Chain of command limits
- Chain of command wraps instance methods on classes, tables, forms, and form data sources. It cannot be applied to static methods or to methods declared final.
- Table extension
- A table extension adds new fields, indexes, relations, and methods to an existing table without overlayering. It is named with the .Extension suffix and saves in its own model.
- Model layering order
- USR sits above CUS, VAR, and SYS. When two models extend the same element, the extension from the higher layer is the one that takes effect at runtime.
- Deployable package
- A zip artifact produced by building the solution on a build machine. It contains compiled models and metadata, is uploaded to the LCS asset library, and is applied to sandbox or production.
- Model management menu
- The Visual Studio Dynamics 365 > Model management menu creates new models, edits model dependencies, and installs models into the development workspace database.
- Best Practice checks
- Static analysis of X++ and metadata run from the Dynamics 365 menu or during a build. Errors stop the build; warnings are reported but allow compilation to continue.
- Build machine role
- A build VM compiles code, runs tests, and generates the deployable package. Development VMs cannot produce packages that are valid for sandbox or production deployment.
- Task recorder
- A client tool that records user actions step by step. Recordings become BPM process documentation or RSAT automation scripts for regression testing.
- Trace Parser
- A standalone analysis tool that reads a trace captured from the web client and reports the slowest SQL statements and the X++ call tree that issued them.
- Transaction table type
- A table type for records created by daily business activity, such as sales lines. It differs from Main, Parameter, Group, Worksheet, and Reference table types.
- Alternate key
- A unique index nominated as the alternate key of a table. It is required before a table can be exposed through OData or a public data entity.
- Data entity staging table
- A generated table that holds imported records while they are validated and mapped. Records move from staging into the target table when the project executes.
- Extensible enum
- An enum whose IsExtensible property is Yes. Other models can add elements to it without overlayering, whereas a non-extensible enum cannot be extended.
- Computed view column
- A column in a view whose value is produced by a SysComputedColumn method returning a SQL expression string, so aggregation happens in the database query.
- ttsbegin and ttscommit
- Statements that open and close an explicit transaction scope. All work inside commits atomically at ttscommit and rolls back if an exception aborts the outermost scope.
- insert_recordset
- A set-based X++ statement that copies rows from a source table into a target table in a single database statement, much faster than looping row by row.
- RecordInsertList
- A buffer object that collects records in memory; insertDatabase() writes the whole buffer in one database call instead of one call per record.
- SysOperation framework
- The pattern for building processes that can run in batch. It uses a service class for logic, a data contract for parameters, and a controller to launch execution.
- SysTest unit test
- A class deriving from SysTestCase whose test methods carry the SysTestMethod attribute. Tests are discovered and run from Visual Studio Test Explorer.
- Report data provider class
- An SSRS data source class extending SRSReportDataProviderBase. It carries report parameter and query attributes and fills a temp table exposed as the dataset.
- Electronic Reporting components
- A configurable reporting framework with three configuration types: data model, model mapping to data sources, and format. Formats change without code deployment.
- Entity store
- An aggregate data store refreshed from the transactional database. It supplies measurements and dimensions to embedded Power BI visuals and analytical workspaces.
- Document Routing Agent
- A client-side Windows service that routes SSRS reports from the web client to network printers, enabling print scenarios that the browser alone cannot provide.
- Data management framework
- A staging-based import and export framework. Users group data entities into projects, map source files, validate in staging, and schedule recurring runs.
- OData endpoint
- Public data entities are exposed at the path /data/{EntityName}. Clients authenticate through an Azure AD app registration and pass an OAuth bearer token.
- Business events
- A framework where a contract class defines the payload and a class deriving from BusinessEventsBase publishes it to an endpoint when a business action occurs.
- Entity change tracking
- A data entity property that records inserts, updates, and deletes so an export can send only the records changed since the previous synchronization run.
- Security hierarchy
- Roles contain duties, duties contain privileges, and privileges grant permissions on entry points, tables, fields, and data entities. Users receive access through roles.
- Extensible data security
- A row-level policy built from a query plus one or more constrained tables and a context type such as role, user, company, or a custom context.
- RunAs method
- A method on the RunAs class that executes a code block under a different user account, granting temporary elevated access without permanently assigning privileges.
- Set-based SQL operations
- update_recordset and delete_from apply one database statement to many rows at once, cutting round trips, lock duration, and overall transaction time.