Microsoft Technology Licensing, LLC

Robert Alan Meyers

Christopher Alan Hays

Jason David Carlson

Carolyn Khanh Chau

Aaron Stephen Meyers

Sachin Patney

Jeremy Jude Alexi Edwards

Benjamin Edward Rampson

Brian L Welcker

Lisa Renee Mueller

Avi Samuel Gavlovski

Poornima Hanumara

Avi Samuel Gavlovski Kaufman

Eric Stephen Meyers

Operating a range slider. A method includes displaying a range slider in a graphical user interface. The method further includes detecting a minimum selecting user interaction on a graphical user interface. The method further includes placing the minimum slider thumb at value on the slider track by placing the inside edge of the minimum slider thumb on the value to select the minimum endpoint of the selected range at the inside edge of the minimum slider thumb. The method further includes detecting a maximum selecting user interaction on the graphical user interface. The method further includes placing the maximum slider thumb at a value on the slider track by placing the inside edge of the maximum slider thumb on the value to select the maximum endpoint of the selected range at the inside edge of the maximum slider thumb.

Touch optimizations for range slider controls

Concepts and technologies are described herein for providing a range filter user interface with selectable range controls that toggle between inclusive and exclusive modes. The range controls visually indicate configuration in an inclusive mode or an exclusive mode. Upon selection of a range control, the range control switches between inclusive and exclusive modes, and provides visual indication of the current mode.

Inclusion/exclusion user interface controls for range filters

Embodiments are directed to determining a data insertion point in a data layout based on relative cardinalities between data objects and to determining a data insertion point in a data layout based on defined hierarchies between data objects. In an embodiment, a computer system receives a user input indicating that an additional portion of information is to be added to an existing data layout which includes multiple different data objects. The computer system accesses the data objects to determine relative cardinalities between the data objects in the data layout. The computer system determines an optimal data insertion point for inserting the additional portion of information based on the determined relative cardinalities between the data objects. The computer system also inserts the additional portion of information in the existing data layout at the determined optimal data insertion point.

Automatic layout derivation and implementation

Various technologies and techniques are disclosed for persisting instance-level report customizations. Input is received from a user to run an original report. An original query associated with the original report is executed against a data store. The original report is displayed to the user. At least one instance-level customization is received from the user to customize an instance of the original report. The instance-level customizations that the user makes to the customized report are tracked in a manner that allows a history of changes from the original report to the customized report to be determined. The customized report is generated in subsequent executions of the report. The instance-level changes the user made to the report can be audited to allow users to see the changes made to the original report.

Persisting instance-level report customizations

Various technologies for processing a selection on an item on a report. In one implementation, a request to perform an action on the item may be received. Whether one or more actions corresponding to the item exist based on one or more parameters and one or more values of the parameters associated with the item may be dynamically determined. A list of one or more actions may be displayed if the one or more actions exist.

Dynamic determination of actions on selected items on a report

Mechanisms are provided for drilling on data elements in arbitrary ad-hoc reports. Data elements in one ad-hoc report can be examined and then drilled on, in order to obtain other related data elements in other ad-hoc reports. Thus, in one exemplary aspect of the disclosure, when a user selects a data element in an ad-hoc report, another ad-hoc report is generated containing data elements that are obtained as a result of taking into account 1) the original query associated with data element in the ad-hoc report; 2) the context of the selection in the ad-hoc report, and 3) the granularity of the resulting query associated with the resulting ad-hoc report.

Drilling on elements in arbitrary ad-hoc reports

A data query and reporting method and system are provided. The method and system allow non-technical computer users to build and execute complex database queries. The method and system accommodate the need for a simple, easy-to-understand interactive and iterative means for generating and validating database queries. The method and system reduce the complexity and costs associated with retrieving useful information for organizations of all sizes, especially smaller businesses. The method and system support a robust security model, enabling organizations to protect sensitive data while providing broad data access.

Method and system for building a report for execution against a data store

A graphical user interface and method of use thereof that allows users to interact with an entity relationship model. The user interface includes zones that allow users to navigate among the entities, roles and fields to create queries that are run against the model. Clicking on an entity in the shows the available fields for the entity. Users can drag and drop entities and fields onto a design surface to quickly and easily build queries. Rules are applied when either an entity or a field is dropped onto the design surface based upon the item being dropped (either an entity or a field), the position of the drop and also the properties that are associated with the item. Entities may be grouped and filtered to sort and limit the results of the query. After query is run, the results may be displayed in a separate area to the user.

User interface mechanism to formulate complex query against an entity relationship model

A preferred path between two selected entities is determined. Initially, there is provided a representation of the data structure in the form of a plurality of entities having relations between them indicative of roles and the relations reflecting a cardinality of one of a one-to-one, one-to-many and a many-to-one relationship between the entities. A query is entered that provides an indication of a first selected entity and a second selected entity. A preferred path is selected through the entities and relations that couples the first selected entity to the second selected entity. The preferred path is selected from a plurality of paths as a function of the number of changes in cardinality along the plurality of paths and a indicator indicative of a preferred role relating two entities.

Growing community of inventors

Redmond, WA, United States of America

Robert Alan Meyers