Abstract: Concepts and technologies are described herein for reducing locking during database transactions without using a cache. In accordance with the concepts and technologies disclosed herein, a server application generates a changeset in response to receiving an operation for modifying base data stored in a database. The changeset is stored as a set of tables that are stored at the database with the base data, and include a first table reflecting records in the base data that have been created and/or modified by the operations. The changeset further can include a second table reflecting records in the base data that have been deleted by the operations.

Abstract: Modeled Types allow a developer to define attributes and/or code when defining a new type. When the Modeled Type is used, specific values may be assigned to the attributes. The consumer of the values of the attributes can be the type itself by executing the logic during application execution, or the consumer may be the runtime framework or the application using the values by querying the meta-data of the Modeled Type. Modeled Type Aliasing defines a Modeled Type based on another Modeled Type allowing both a new unique name but at the same time optionally supplying specific values to one or more of the attributes of the base Modeled Type. Context-aware Modeled Types provide a description of how to determine the value for the attribute.

Abstract: A debugging tool is provided that is capable of recording code paths taken during a program's execution, and along the way capture the memory state at configurable points in time such as function exits or statements. The tool also records interactions with external systems like a database, and captures which statements resulted in interactions with these systems. An analysis of the output of the debugging tool enables a developer to understand which part of the code executed; what the value of relevant variables were at configurable points in time; and which code statements correlate to which interactions with external systems.

Abstract: A reusable ERP data retrieval object, in particular, a wide application query object provides a systematic and standardized approach to data retrieval. In one embodiment, the wide application query object is an encapsulated query object in that multiple queries are aggregated into one master query object (i.e., the wide application query object) that can, but does not necessarily have to, span multiple disparate data sources. In another embodiment, data retrieved in accordance with the wide application query logic is manipulated by code in any of a variety of different ways using a trigger model and specialized constructs. In still another embodiment, public parameters are utilized to trigger functions that impact the substance and layout of the query output.

Abstract: Debugging operations on individual client sessions for a remotely executed shared application are enabled to be performed as the client requests are processed on the executing server without disrupting execution of other client sessions. A remote debugging client may connect to a debugging engine executed on the server allowing the debugging client to view source code, set breakpoints, view client connections, and receive callbacks or notifications when a breakpoint is hit by the client session being debugged. The debugging client may also control execution by stepping through client code enabling debugging of multiple clients simultaneously.

Abstract: Concepts and technologies are described herein for reducing locking during database transactions without using a cache. In accordance with the concepts and technologies disclosed herein, a server application generates a changeset in response to receiving an operation for modifying base data stored in a database. The changeset is stored as a set of tables that are stored at the database with the base data, and include a first table reflecting records in the base data that have been created and/or modified by the operations. The changeset further can include a second table reflecting records in the base data that have been deleted by the operations.

Abstract: A debugging tool is provided that is capable of recording code paths taken during a program's execution, and along the way capture the memory state at configurable points in time such as function exits or statements. The tool also records interactions with external systems like a database, and captures which statements resulted in interactions with these systems. An analysis of the output of the debugging tool enables a developer to understand which part of the code executed; what the value of relevant variables were at configurable points in time; and which code statements correlate to which interactions with external systems.

Abstract: A checkpoint system is provided to quickly identify differences or deltas between a baseline version and a modified version of a database and to quickly restore the database to the baseline version using the deltas. The checkpoint system identifies the deltas between versions of the database by a rapid comparison of the rows of each table within a baseline version and a modified version of the database. The checkpoint system can use the rapid comparison when testing to identify sets of deltas resulting from performing an old procedure on a test database and a new procedure on the test database. The rapid comparison can be applied to these sets of deltas to identify differences resulting from the new procedure. The deltas can also be used to rapidly restore a database from a modified version to a baseline version.

Abstract: Debugging operations on individual client sessions for a remotely executed shared application are enabled to be performed as the client requests are processed on the executing server without disrupting execution of other client sessions. A remote debugging client may connect to a debugging engine executed on the server allowing the debugging client to view source code, set breakpoints, view client connections, and receive callbacks or notifications when a breakpoint is hit by the client session being debugged. The debugging client may also control execution by stepping through client code enabling debugging of multiple clients simultaneously.

Abstract: Embodiments of the present invention pertain to implementation of textual names as the actual identifiers of elements of models. A structured system provided for constructing the textual names so as to be unique in a specific context. In one embodiment, namespaces are added to a name as a mechanism for ensuring uniqueness across multiple development sources. In one embodiment, upon deployment to a runtime environment, alternate names are assigned to support efficient processing.

Abstract: A method and system for hierarchical caching of objects of an ERP system is provided. A caching system comprises a server cache component that is executed by a server and a client cache component that is executed by each client of the server. The server cache component maintains a server cache at the server, and the client cache component maintains a client cache at each client. The client cache components also cache the objects in local client caches. Upon opening an object, the client cache component checks its local client cache to determine whether the object is cached. If so, then the client cache component need not retrieve the object from the server. Thus, the caching system is hierarchical in that each server and client maintains its own cache.

Abstract: A system and method directed to capturing the structure of data models using entity patterns is provided wherein an entity pattern is an abstraction, for example in the MICROSOFT BUSINESS FRAMEWORK® (MBF), that surfaces in the model editor of the framework at the root level and consists of one or more entity roles that together define a structural pattern of a model. The entity pattern may be considered as an über-model, or a model template for a model. Prescriptive rules are added to the design of entities, required properties and relations to other entities (entity roles). Applications of the entity patterns are validated at design time. The runtime framework supports any applied pattern and invokes the pattern specific code. It is a general advantage that the runtime operation is model driven and interprets the model data at runtime. The application and usage of a pattern is part of the model of the application/software program.

Abstract: A system and method directed to capturing the structure of data models using entity patterns is provided wherein an entity pattern is an abstraction, for example in the MICROSOFT BUSINESS FRAMEWORK®(MBF), that surfaces in the model editor of the framework at the root level and consists of one or more entity roles that together define a structural pattern of a model. The entity pattern may be considered as an über-model, or a model template for a model. Prescriptive rules are added to the design of entities, required properties and relations to other entities (entity roles). Applications of the entity patterns are validated at design time. The runtime framework supports any applied pattern and invokes the pattern specific code. It is a general advantage that the runtime operation is model driven and interprets the model data at runtime. The application and usage of a pattern is part of the model of the application/software program.

Abstract: A checkpoint system is provided to quickly identify differences or deltas between a baseline version and a modified version of a database and to quickly restore the database to the baseline version using the deltas. The checkpoint system identifies the deltas between versions of the database by a rapid comparison of the rows of each table within a baseline version and a modified version of the database. The checkpoint system can use the rapid comparison when testing to identify sets of deltas resulting from performing an old procedure on a test database and a new procedure on the test database. The rapid comparison can be applied to these sets of deltas to identify differences resulting from the new procedure. The deltas can also be used to rapidly restore a database from a modified version to a baseline version.

Abstract: The customization system receives an application model that contains one or more elements stored in a database. The customization system receives a modification to an element of the application model. The customization system stores the modification to the element separately from the application model such that the application model is accessible in either a modified or unmodified state. Thus, multiple third parties can make changes to the same application model elements and business logic without causing conflicts with each other. In addition, updates and patches to the enterprise resource planning system can be applied with less likelihood that the customizations will be negatively affected.

Abstract: Embodiments of the present invention pertain to implementation of textual names as the actual identifiers of elements of models. A structured system provided for constructing the textual names so as to be unique in a specific context. In one embodiment, namespaces are added to a name as a mechanism for ensuring uniqueness across multiple development sources. In one embodiment, upon deployment to a runtime environment, alternate names are assigned to support efficient processing.

Abstract: Modeled Types allow a developer to define attributes and/or code when defining a new type. When the Modeled Type is used, specific values may be assigned to the attributes. The consumer of the values of the attributes can be the type itself by executing the logic during application execution, or the consumer may be the runtime framework or the application using the values by querying the meta-data of the Modeled Type. Modeled Type Aliasing defines a Modeled Type based on another Modeled Type allowing both a new unique name but at the same time optionally supplying specific values to one or more of the attributes of the base Modeled Type. Context-aware Modeled Types provide a description of how to determine the value for the attribute.

Abstract: A system and method directed to capturing the structure of data models using entity patterns is provided wherein an entity pattern is an abstraction, for example in the MICROSOFT BUSINESS FRAMEWORK® (MBF), that surfaces in the model editor of the framework at the root level and consists of one or more entity roles that together define a structural pattern of a model. The entity pattern may be considered as an über-model, or a model template for a model. Prescriptive rules are added to the design of entities, required properties and relations to other entities (entity roles). Applications of the entity patterns are validated at design time. The runtime framework supports any applied pattern and invokes the pattern specific code. It is a general advantage that the runtime operation is model driven and interprets the model data at runtime. The application and usage of a pattern is part of the model of the application/software program.

Abstract: A system and method directed to capturing the structure of data models using entity patterns is provided wherein an entity pattern is an abstraction, for example in the MICROSOFT BUSINESS FRAMEWORK®(MBF), that surfaces in the model editor of the framework at the root level and consists of one or more entity roles that together define a structural pattern of a model. The entity pattern may be considered as an über-model, or a model template for a model. Prescriptive rules are added to the design of entities, required properties and relations to other entities (entity roles). Applications of the entity patterns are validated at design time. The runtime framework supports any applied pattern and invokes the pattern specific code. It is a general advantage that the runtime operation is model driven and interprets the model data at runtime. The application and usage of a pattern is part of the model of the application/software program.