Microsoft Technology Licensing, LLC

David Robert Shutt

Philip Alan Bernstein

Shankar Pal

Michael J McCormack

Nicholas James Thomson

Dmitri Davydok

Indrojit Deb

Elizabeth Ann Nichols

Andrew Robert Miller

Thomas F Bergstraesser

Michael James Ott

Alexander M Tkatch

Ramesh Thimmarajarasu Bangalore

Prabhat Kumar Pandey

Elliot Stephenson Lewis

Jasjit Singh Grewal

Steven M Cellini

Bradley J Barrows

Jeremy M Kolpak

Jagan Peri

Marshall Scot Bjerke

Robert Tobkes

Bryan David Cooke

Jonathan Wayne Phillips

Hao Sun

John Grant Bennett

Abhishek Agarwal

Nishant Dani

Arash Ghanaie-Sichanie

Roy A Leban

Neeraj Ahuja

Derik Bjorn Stenerson

Abhijit Gore

Joseph N Coco

Shashi Ranjan

Apurva F Dalia

Jeffrey H Alger

Craig Allen Harry

Akezyt Janedittakarn

Dominic Justin Pouzin

Nirav Girish Shah

Kulothungan Rajasekaran

Sandhya Vankamamidi

Niraj Yadav

Daniel Doubrovkine

David A Marshall

Adithya Nittor Vishwanath

Sutirtha Saha

Barry I Kelman

Sachin Kukreja

Ramani Jagadeba

Manjeet Bothra

Suwat Chitphakdibodin

Ilana Rae Smith

Brad Dean Thompson

Koushik Bhattacharjee

Sharad Sharma

Douglas William Wood

Paul Jonathon Sanders

Kunal Garg

Ankit Malpani

Edward Martinez

Abhishek Kumar Gupta

Kulo Rajasekaran

Ramesh Prasad Pandey

Shan Jiang

Wei-Qiang Michael Gui

On a client computer, customer relationship management software is integrated into a messaging application that includes a user interface. Customer relationship management (CRM) information is received from a server computer. An automatic determination is made as to whether the received CRM information is to be cached on the client computer. When it is determined that the CRM information is to be cached on the client computer, the CRM information is cached in a cache on the client computer. When at least some of the CRM information is cached on the client computer, the cached CRM information is displayed as a view on the client computer. The display of the CRM information is integrated into the user interface of the messaging application program.

Cached and server views with automatic caching and smooth scrolling

A tenant comprising one or more users receives services from a cloud computing system ('CCS'). The CCS determines when a tenant is not using any services, and if so, the CCS initiates a tenant suspension process. The tenant suspension process involves suspending various asynchronous computing processes for the tenant, which execute otherwise execute even if no users of the tenant are currently accessing the CCS. After a period of non-use of the CCS, the tenant is suspended. The tenant is returned to an active state automatically when a user of the tenant logs-on to receive services.

Managing capacity in a data center by suspending tenants

A hosted multi-tenant application is provided that permits a tenant to self-manage aspects of the operation of the application. A tenant may be permitted to upgrade the multi-tenant application on-demand or according to a schedule, to place the multi-tenant application into a read-only mode of operation, to create a shadow copy of their unshared organization database, to merge changes to a shadow copy into a master version of the unshared organization database, to create and revert to snapshots of an unshared organization database, and to perform other functions. A computing architecture that utilizes site-wide server computers and scale groups may be utilized to implement this functionality.

Tenant management of a hosted multi-tenant application

A data reporting framework that works across on-premise and hosted Customer Relationship Management (CRM) platforms enabling definition and execution of secure custom reports is provided. A fetch query language of a CRM platform is used along with reporting service tools and constructs to enable users to upload and execute custom fetch based reports with support for expressions, code, formatting, and drill through. Users are also enabled to build simple reports from within CRM and, if needed, enhance those reports using reporting service tools and re-upload in CRM. Furthermore, custom reports may be executed in a sandboxed environment to provide full security in a multi-tenant, hosted CRM system.

Data reporting framework across on-premise and hosted CRM services

Technologies are described herein for implementing a hosted multi-tenant application system. The server computers utilized to provide the hosted application are organized into logical groupings of server computers called scale groups. One or more tenants are assigned to each scale group. When a new tenant is provisioned, the tenant is assigned to a scale group and a database server in the assigned scale group creates a database for the tenant. An association between the tenant and the scale group is also created in a shared configuration database. When a request is received from a tenant to access the hosted application, the shared configuration database is consulted to locate the scale group hosting the tenant. Once the appropriate scale group has been located, the request is redirected to the appropriate scale group for processing.

Multi-tenant hosted application system

Techniques for an inherited entity storage model are described that can be employed to implement inherited entity management for a CRM system. In at least some embodiments, input can be obtained to create a custom entity that is based at least in part upon a parent entity. The custom entity is created to inherit the parent entity according to an inheritance relationship established between the entities. To do so, the custom entity is created from the parent entity in a common table with the parent entity using some common fields and defining custom fields as appropriate. Data for the entities is then stored via the common table. This approach can reduce storage requirements, enable unified searching, and speed up data operations. Further, back-end business logic associated with parent entity in the CRM system can be automatically applied to the custom entity based upon the inheritance relationship established between the entities.

Inherited entity storage model

Concepts and technologies are described herein for managing recurring appointments without losing historical data associated with the recurring appointments. In accordance with the concepts and technologies disclosed herein, a recurring appointment definition can be modified without deleting the recurring appointment definition and/or losing exceptions, notes, and/or other data associated with the recurring appointment definition. Additionally, the concepts and technologies disclosed herein allow the modification of an existing recurring appointment definition without creating a new recurring appointment definition. Thus, synchronization between rules-based calendaring applications and expansion-based calendaring applications can be accomplished without creating multiple instances of related recurring appointments created due to modifications of the recurring appointment definition.

Managing recurring appointments

Technologies are described herein for providing a bi-direction e-mail transport between a management ('CRM') server computer and an e-mail server computer. An e-mail connector communicates with a CRM server computer to determine whether any e-mail messages are pending send at the CRM server computer. If any e-mail messages are pending send, the e-mail connector retrieves the e-mail messages from the CRM server computer. The e-mail connector then communicates with an e-mail server computer to send the retrieved e-mail messages to their intended recipients. The e-mail connector may also retrieve e-mail messages from the e-mail server computer and determine whether the e-mail messages are CRM related. If the e-mail messages are CRM related, the e-mail connector is operative to transmit the CRM-related e-mails to the CRM server.

Electronic mail connector

Technologies are described herein for providing a hosted multi-tenant application that utilizes per-tenant unshared private databases. A shared middle-tier is utilized in conjunction with private, unshared databases for each of the tenants. The private, unshared databases are utilized to store application data for an associated tenant, along with any customizations to the application implemented by the tenant. A shared configuration database is also utilized that stores application data that is shared among the tenants. When a request is received from a tenant to access the hosted application, the shared configuration database is utilized to locate the private, unshared database associated with the tenant making the request. The contents of the private, unshared database associated with the tenant making the request are then utilized to response to the request.

Hosted multi-tenant application with per-tenant unshared private databases

Various embodiments of the present invention are directed toward extending a federation of servers and balancing the data load of said federation of servers, in order to improve accessibility and scope of the system by moving the first backup data structure on the second server to the new server, creating a second data structure on the new server, and creating a second backup data structure for the second data structure on the second server. To balance the load, certain embodiments employ a method comprising suspending writes to the selected logical partitions, copying selected logical partitions to the new physical partition, redirecting reads and writes to the logical partitions in the new physical partition, and removing the original selected logical partitions. Alternative embodiments for balancing data load comprise the substitute steps of creating a temporary replication stream for the selected logical partitions to the new physical partition, copying selected logical partitions to the new physical partition, deconflicting inconsistencies in the logical partitions on the new physical partition, redirecting reads and writes for the selected logical partitions to the logical partitions in the new physical partition, and removing the original selected logical partitions that were copied to the new physical partition.

Systems and methods for the repartitioning of data

Maintaining versions and workspaces in an object repository is disclosed. The system provides an efficient way to manage versions of objects by only copying objects when absolutely necessary, i.e. when a property value in a particular object has changed. In addition, the system provides a mechanism to control whether or not relationships are propagated to successor versions of an object. A further aspect of the system is that resolution of objects during a relationship traversal can be customized depending on whether or not an application accessing the objects is version-aware. If the application is not version aware, a means for resolving the relationship to a particular object is provided. A still further aspect of the system is that merge behavior is parameterized. When two versions of an object are merged, flags control how conflicts in property values and relationship contents are managed. Finally, the system provides a workspace that acts as a virtual repository session and provides workspace context and scope to repository objects.

Versions and workspaces in an object repository

Growing community of inventors

Seattle, WA, United States of America

David Robert Shutt