Microsoft Technology Licensing, LLC

Xiaohong Mark Yang

LuMing Wang

Peter Eberhardy

Zhenyu Tang

Anton Amirov

Peiyuan Yan

Sridharan Ramanathan

George Randall Dong

Patrick John Baumgartner

Lakshmi Narayanan Thanu

Sonal Jain

Rou-Peng Huang

Sanjay Jacob

Hailei Zhang

Jeffrey Wang

Randy Dong

Dylan Hai Huang

Pablo Jose Barvo

Lewis Charles Levin

Alisson A S Sol

Baomin Li

Jason Malcolm

Hai Huang

Kevin Robert Schmidt

Scott Sebelsky

Peter Bull

Robert L Vogt

Patricia O'Connor Sebelsky

Data cells in a spreadsheet report are collapsed and expanded without disrupting other spreadsheet data. A user may want to drill down on data corresponding to a parent member of the report to display more detailed information about the parent member. Likewise, a user may want to drill up the displayed information corresponding to the parent member to hide detailed information associated with the parent member. Before expanding or collapsing a report, the spreadsheet is scanned for information to determine whether the display of other data in the spreadsheet would be disrupted by the expansion/collapse. The information may include cross join information associated with the parent member, the number of child members associated with the parent member, the dimension of the report created by the parent member and the associated child members, and other reports that may be linked to the report that includes the parent member.

Collapsing data cells in one or more reports in a spreadsheet

An object oriented search mechanism extracts structural metadata and data based on type of document contents and data sources connected to the documents. Relationships between textual and non-textual elements within documents as well as metadata associated with the elements and data sources are utilized to generate a unified object model with the addition of semantic information derived from metadata and taxonomy, which are used to enhance search indexing, ranking of search results, and dynamic adjustment of result rendering user interface with fine tuned relevancy. Additional data from data sources connected to the documents may also be used to unlock hidden data such as data that has been filtered out in an original document.

Object oriented data and metadata based search

Technologies are described herein for defining the scope of a sub-cube based upon a database query. A request is received to perform a query of a multi-dimensional database, such as a cube, stored at a server computer. In response to the request, the scope for a sub-portion, called a sub-cube, of the multi-dimensional database is determined based upon the query. The scope of the sub-cube may be determined by identifying the minimum sub-portion of the cube necessary to perform the query. Once the scope has been determined, the sub-cube is generated at the server computer and transmitted to a client computer. The client computer stores the sub-cube locally and performs the requested database query on the sub-cube stored at the client computer. A user interface may be provided through which a user can modify the scope of the sub-cube determined based upon the query.

Defining sub-cube scope based upon a query

Relationships between linked and/or embedded documents as well as documents sharing data source(s) are captured and rendered through virtual documents. Virtual documents are created representing linked/embedded documents and data sources associated with a relevant document. Relationships between real and virtual documents are preserved and rendered along with search results providing a user a comprehensive picture of search results.

Indexing and searching employing virtual documents

Data cells in a spreadsheet report are collapsed and expanded without disrupting other spreadsheet data. A user may want to drill down on data corresponding to a parent member of the report to display more detailed information about the parent member. Likewise, a user may want to drill up the displayed information corresponding to the parent member to hide detailed information associated with the parent member. Before expanding or collapsing a report, the spreadsheet is scanned for information to determine whether the display of other data in the spreadsheet would be disrupted by the expansion/collapse. The information may include cross-join information associated with the parent member, the number of child members associated with the parent member, the dimension of the report created by the parent member and the associated child members, and other reports that may be linked to the report that includes the parent member.

Method for expanding and collapsing data cells in a spreadsheet report

A secure framework for authoring and execution of user-entered database scripts, rules, procedures and other forms of programming is provided. A performance management application is used as an interface between a client data modeling, manipulation or analysis application and one or more data sources or analysis services to prevent malicious or inadvertent implementation of harmful, damaging and/or unauthorized new or modified scripts, rules, procedures or other forms of programming to one or more data sources or data analysis/manipulation services that may be used for retrieving, storing, modifying or using data contained in or affected by the one or more data sources or data analysis/manipulation services.

Secure authoring and execution of user-entered database programming

An interface for designing a report is provided, with elements of the report being disposed at intersections of report positions and configured to present information derived from data in a database. A formula is associated with one or more selected elements in the report to generate a result for the one or more selected elements. A tuple identifying the report positions of the one or more selected elements is associated and stored with the formula in a formula list associated with the report. The report is configured so that, when the report is generated, it is determined whether identifying report positions corresponding to an identified element in the report correspond with the tuple in the formula list. Upon determining the tuple corresponds with the identifying report positions for the identified element, the formula associated with the tuple is applied to generate the result.

Method for capturing design-time and run-time formulas associated with a cell

Financial intelligence architecture that employs financial types that are combined with rules to build financial behavior into the product. Types have behaviors such that types can be assigned that lead to the physical creation of underlying code which embodies the behaviors. Extensibility is provided at least by type parameterization and new type creation. Because types are a design time experience, types are two-way and can be modified, even after instantiation. This allows for mixing and matching of types and underlying behavior giving the system more flexibility at design time while providing a huge simplification of all the details that actually go into such financial applications. The type library is a set of rules that produce metadata, which metadata is later processed by a separate engine to produce the physical schema. The type library defines the basic interactions, data types, and behaviors for predefined dimensions in the system.

Type-driven rules for financial intellegence

Tools and techniques are described for selecting member sets for generating asymmetric queries. User interfaces provided by this description may include representations of different dimensions that include respective members. These dimensions define hierarchical data structures against which queries are run to generate requested reports. The user interfaces may include representations of members associated with different dimensions, with members from different dimensions arranged in selected orders. The user interfaces may also provide selection tools that activate symmetrical or asymmetrical rendering modes for constructing the query. In the symmetrical rendering mode, the query cross-joins all of the members selected from one dimension with all of the members selected from the other dimension. In the asymmetrical rendering mode, the query cross-joins the first-ordered member from one dimension with the first-ordered member from another dimension, cross-joins the second member from one dimension with the second member from another dimension, and so on.

Selecting member sets for generating asymmetric queries

Computer-implemented methods, computer-readable media, and an application system are disclosed for creating and deploying metadata-generated applications. Access is provided to one or more type libraries that each include one or more defined object types configurable for use in generating the application. The defined object types include data structure types, rule types, and data types. Input is elicited from a user regarding desired content and function of the application. Based on the user input, metadata is generated to adapt the defined object types to generate the application. Metadata is generated to adapt the defined data structure types to create one or more application databases, to adapt the defined rule types to create one or more application behaviors, and to adapt the defined data types to create one or more application data types.

Metadata-based application deployment

Sharable extended cell information is used by multidimensional data models to enable cell annotations and line item details. Annotations are notes stored with a cell in a multidimensional dataset. Line item details permit levels of numeric detail below the lowest dimensional granularity. When receiving a multidimensional dataset in response to a query, a client application receives indicator information at the cell level, indicating to the client application that extended cell information is retrievable.

Extended cell information in multidimensional data models

Data allocation is performed by translating a rule set to a query list. An allocation engine receives the rule set and the data and generates a query list. The query list may be in MDX or SQL syntax. After modifying the queries in the list into a list of physical queries that match the specific characteristic of the data store, a modeling abstraction layer provides the physical queries to the data store engine to perform the queries and provide the results to the allocation engine. The allocation engine allocates the data among existing or new hierarchical levels based on the query results. The allocated data may be stored in the same data store as the original data.

Using multi-dimensional expression (MDX) and relational methods for allocation

Embodiments are provided to use metadata to provide readable and/or writeable regions of a multi-dimensional space. In an embodiment, metadata can be used to define readable and/or writeable regions of a multi-dimensional data store. The various embodiments also use relational and/or multi-dimensional representations to resolve and validate readable and/or writeable regions of a multi-dimensional space. Metadata can also be used to designate a number of writeable and/or readable regions of a relational and/or multi-dimensional representation.

Growing community of inventors

Sammamish, WA, United States of America

Xiaohong Mark Yang