Abstract: A computer system identifies an information set stored at a data store. The computer system then identifies first metadata that includes first instructions indicating how the information set is to present a plurality of data items, and second pre-existing metadata that includes second instructions indicating how the information set is to present the plurality of data items. The computer system determines that a portion of the first metadata will override a portion of the second metadata, to create combined metadata. The computer system provides the combined metadata to the information set, including combining the second metadata with the first metadata by at least overriding the second instructions of the second metadata with the first instructions of the first metadata. The computer system presents the plurality of data items in accordance with the second metadata, at least as modified by the first instructions of the first metadata.

Abstract: A computer system identifies an information set stored at a data store. The computer system then identifies first metadata that includes first instructions indicating how the information set is to present a plurality of data items, and second pre-existing metadata that includes second instructions indicating how the information set is to present the plurality of data items. The computer system determines that a portion of the first metadata will override a portion of the second metadata, to create combined metadata. The computer system provides the combined metadata to the information set, including combining the second metadata with the first metadata by at least overriding the second instructions of the second metadata with the first instructions of the first metadata. The computer system presents the plurality of data items in accordance with the second metadata, at least as modified by the first instructions of the first metadata.

Abstract: A computer system identifies an information set stored at a data store. The computer system then identifies first metadata that includes first instructions indicating how the information set is to present a plurality of data items, and second pre-existing metadata that includes second instructions indicating how the information set is to present the plurality of data items. The computer system determines that a portion of the first metadata will override a portion of the second metadata, to create combined metadata. The computer system provides the combined metadata to the information set, including combining the second metadata with the first metadata by at least overriding the second instructions of the second metadata with the first instructions of the first metadata. The computer system presents the plurality of data items in accordance with the second metadata, at least as modified by the first instructions of the first metadata.

Abstract: Embodiments described herein are directed to providing enhanced database editing and reporting capabilities. In one scenario, a computer system receives a data item request that identifies which data items are to be reported. The computer system accesses a relational data store to determine which information sets are to be used for reporting the requested data items. Based on the determination, the computer system accesses those information sets that are to be used in the reporting the requested data items. The computer system then determines that metadata has been provided for at least one of the accessed information sets. The metadata includes instructions at least partially indicating how the data items are to be reported. The computer system also reports the data items according to the instructions in the provided metadata, regardless of how the data items are to be reported using the existing information sets.

Abstract: Embodiments described herein are directed to providing enhanced database editing and reporting capabilities. Embodiments include a computer system receiving a database query including a request to edit one or more data items in the database. The computer system determines which data items would be affected by the requested data item edit. Based on the determination, the computer system accesses those data items that would be affected by the requested data item edit. The computer system retrieves metadata for each data item that would be affected by the requested data item edit. The metadata includes information at least partly indicating how the edit is to be performed. The computer system also performs the edit to affect the data items according to at least a portion of the retrieved metadata, regardless of how the edit would otherwise have been performed based on existing knowledge about the affected data items.

Abstract: In one embodiment, a computer system generates a view of entities associated with varying data types for presentation on a generic viewer. The entities and data types have relationships as defined in a corresponding schema. The schema is stored as data in a repository with the data types. The computer system receives an edit request configured to change various selected entities, where each entity has an associated data type, queries the repository to determine various properties of the selected entities corresponding to the received edit request including the data type, and determines, based on the schema, that the edit is valid based on relationship information stored in the schema. The computer system also sends the validated edit information to the generic viewer for presentation. The generic viewer has no prior knowledge of how to handle the selected entities and corresponding data types.

Abstract: Embodiments described herein are directed to providing enhanced database editing and reporting capabilities. In one scenario, a computer system receives a data item request that identifies which data items are to be reported. The computer system accesses a relational data store to determine which information sets are to be used for reporting the requested data items. Based on the determination, the computer system accesses those information sets that are to be used in the reporting the requested data items. The computer system then determines that metadata has been provided for at least one of the accessed information sets. The metadata includes instructions at least partially indicating how the data items are to be reported. The computer system also reports the data items according to the instructions in the provided metadata, regardless of how the data items are to be reported using the existing information sets.

Abstract: Facilitating generic database editing to allow for data to be received from a user for entry into a database without requiring the data to conform to schema constraints for the database. A method includes examining a first schema for a first database. The first schema including a first set of constraints specified in the first schema on data to be entered into the first database. The method further includes, based on the examination, constructing a second database corresponding to the first database. The second database is associated with a second schema with a second set of constraints. The second set of constraints is a relaxed version of the first set of constraints specified in the first schema.

Abstract: Facilitating generic database editing to allow for data to be received from a user for entry into a database without requiring the data to conform to schema constraints for the database. A method includes examining a first schema for a first database. The first schema including a first set of constraints specified in the first schema on data to be entered into the first database. The method further includes, based on the examination, constructing a second database corresponding to the first database. The second database is associated with a second schema with a second set of constraints. The second set of constraints is a relaxed version of the first set of constraints specified in the first schema.

Abstract: Embodiments are directed to dynamically building software applications and dynamically updating software applications based on changed data values. In one embodiment, a computer system receives an indication that a software application is to be initiated. The computer system also receives an application description including tags describing software objects that are to be included in the software application, automatically maps portions of the application description identified by the tags to software objects using reflection, where the reflecting includes accessing properties associated with the software objects, and automatically binds properties of the software objects to the portions of the application description based declarative rules included in the software object properties associated with the software object.

Abstract: Embodiments described herein are directed to generating a customized data viewer, where the viewer is configured to display data at any level in a data model. In one embodiment, a computer system receives a user request indicating that portions of data are to be displayed in a user-customized manner using a data viewer. The computer system accesses the requested data portions that are to be displayed with the data viewer. The computer system generates a dynamic data viewer configured to display the accessed data portions in the user-customized manner indicated in the received user request. The computer system also applies the generated dynamic data viewer to the accessed data portions, such that the generated viewer displays the requested data portions in the user-customized manner.

Abstract: Facilitating generic database editing to allow for data to be received from a user for entry into a database without requiring the data to conform to schema constraints for the database. A method includes examining a first schema for a first database. The first schema including a first set of constraints specified in the first schema on data to be entered into the first database. The method further includes, based on the examination, constructing a second database corresponding to the first database. The second database is associated with a second schema with a second set of constraints. The second set of constraints is a relaxed version of the first set of constraints specified in the first schema.

Abstract: Embodiments described herein are directed to generating a customized data viewer, where the viewer is configured to display data at any level in a data model. In one embodiment, a computer system receives a user request indicating that portions of data are to be displayed in a user-customized manner using a data viewer. The computer system accesses the requested data portions that are to be displayed with the data viewer. The computer system generates a dynamic data viewer configured to display the accessed data portions in the user-customized manner indicated in the received user request. The computer system also applies the generated dynamic data viewer to the accessed data portions, such that the generated viewer displays the requested data portions in the user-customized manner.

Abstract: Embodiments described herein are directed to dynamically reconfiguring at least a portion of an operating software application. In one embodiment, a computer system receives an edit indicating that at least one portion of an operating software application is to be edited, where the edit includes changes that are to be dynamically applied to the application. The computer system instantiates dynamic configuration builders designed to implement application changes as indicated by the received edit and determines which portions of the application are to be suspended while the changes to the application are implemented. The computer system suspends the determined application portions until the application changes are implemented and implements the changes indicated by the edit on the suspended portion of the application, while the remainder of the application continues operating.

Abstract: Embodiments are directed to dynamically building software applications and dynamically updating software applications based on changed data values. In one embodiment, a computer system receives an indication that a software application is to be initiated. The computer system also receives an application description including tags describing software objects that are to be included in the software application, automatically maps portions of the application description identified by the tags to software objects using reflection, where the reflecting includes accessing properties associated with the software objects, and automatically binds properties of the software objects to the portions of the application description based declarative rules included in the software object properties associated with the software object.

Abstract: Embodiments described herein are directed to the constructing software applications based on data models and automatically reconfiguring runtime object graphs according to data model edits input by a user. In one embodiment, a computer system performs a method for constructing at least a portion of a software application based on a data model. The computer system accesses a data model that includes user-configurable construction information indicating how at least a portion of a software application is to be constructed. The declarative interpreter is configured to construct an application based on the construction information in the data model. The computer system interprets the construction information in the data model to determine how to construct at least a portion of the software application. The computer system also constructs at least a portion of the software application based on the interpretation of the construction information in the data model.

Abstract: In one embodiment, a computer system generates a view of entities associated with varying data types for presentation on a generic viewer. The entities and data types have relationships as defined in a corresponding schema. The schema is stored as data in a repository with the data types. The computer system receives an edit request configured to change various selected entities, where each entity has an associated data type, queries the repository to determine various properties of the selected entities corresponding to the received edit request including the data type, and determines, based on the schema, that the edit is valid based on relationship information stored in the schema. The computer system also sends the validated edit information to the generic viewer for presentation. The generic viewer has no prior knowledge of how to handle the selected entities and corresponding data types.