Customization conflict detection and resolution

• US 7,721,158 B2
• Filed: 06/04/2007
• Issued: 05/18/2010
• Est. Priority Date: 06/04/2007
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Lee, Michael
• Primary Examiner(s): Lohn; Joshua A
• Application Number:
  US11/810,123
• Publication Number:
  US 20080301486A1
• Time in Patent Office: 1,079 Days
• Field of Search: 714/38, 714/48, 717/168, 717/170
• US Class Current: 714/48
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A computer-implemented method is disclosed for managing customization conflicts. The method includes receiving an indication of a conflict. The conflict is indicative of an error created by a customization of a core application. A customization correction is identified as a remedy for the customization conflict. The customization correction is transmitted over a network to a party affiliated with a system affected by the customization conflict.

Claims

1. A computer-implemented method for managing customization conflicts, comprising:

receiving an indication of an automatically detected conflict, the conflict being caused by a metadata error created by a first customization of a core application, the metadata error being an inconsistency created when the first customization has caused a change to a static metadata component, the static metadata component being depended upon by a second customization of the core application, the first customization operating on a first computing device that is separate and distinct from a second computing device upon which the second customization operates;

utilizing a computer processor that is a component of the computer to identify, from a database of conflict corrections, a customization correction configured to remedy the conflict; and

transmitting, over a network, data related to the customization correction for processing to correct the metadata error.

2. The method of claim 1, wherein transmitting comprises transmitting over the Internet.

3. The method of claim 1, wherein receiving an indication of an automatically detected conflict comprises receiving an indication of a runtime conflict.

4. The method of claim 1, wherein the change to the static metadata component is an elimination of a particular method from a class, the particular method being depended upon by the second customization.

5. The method of claim 1, wherein the change to the static metadata component is an elimination of a field.

6. The method of claim 1, wherein the change to the static metadata component is an addition of a control to a form.

7. A computer-implemented method for managing customization conflicts, the method comprising:

receiving an indication of an automatically detected runtime customization conflict, the runtime customization conflict being caused by an error that has occurred due to an inconsistency in runtime logic;

utilizing a computer processor that is a component of the computer to identify, from a plurality of customizations of a core application operating on separate and distinct computing devices, a customization that is responsible for creating the automatically detected runtime customization conflict; and

transmitting, over a network to an entity responsible for the identified customization, a collection of data related to the customization conflict.

8. A customization conflict management system, comprising:

a network-based service component that receives a remotely transmitted indication of a conflict, the conflict being caused by a metadata error created by a first customization of a core application, the metadata error being an inconsistency created when the first customization has caused a change to a static metadata component, the static metadata component being depended upon by a second customization of the core application, the first customization operating on a first computing device that is separate and distinct from a second computing device upon which the second customization operates;

a database of conflict corrections;

a computer processor that identifies, from the database of conflict corrections, a customization correction configured to remedy the conflict; and

wherein the network-based service component transmits, over a network, a record of the customization correction for processing to correct the metadata error.

9. The system of claim 8, wherein the conflict is a runtime conflict.

10. The system of claim 8, wherein the change to the static metadata component is an elimination of a particular method from a class, the particular method being depended upon by the second customization.

11. The system of claim 8, wherein the change to the static metadata component is an elimination of a field.

12. The system of claim 8, wherein the change to the static metadata component is an addition of a control to a form.

13. The system of claim 8, wherein the change to the static metadata component is a change to a static property.