RESOLVING CONFLICTS WHEN IMPORTING AN APPLICATION CUSTOMIZATION

• US 20090119345A1
• Filed: 11/01/2007
• Published: 05/07/2009
• Est. Priority Date: 11/01/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Davydok, Dmitri, Balasubramanyan, Balaji
• Granted Patent: US 8,671,390 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

A conflict resolution system allows an end user to export customizations to an application program so that the customizations can be imported by another end user. The conflict resolution system may export a customization by outputting metadata describing the customization. When the customization is a custom property, the metadata may include the name of the entity with which the property is associated, the name of the property, the type of the property, a globally unique identifier for the property, the location on the user interface for the input field for the custom property, and so on. End users may want to share not only their customizations but also the underlying data associated with a customization. When a conflict occurs during import of a customization alone without the data, then the conflict resolution system resolves the conflict in favor of the imported property. When a conflict occurs during import of a customization with data, the conflict resolution system resolves the conflict in favor of the existing property.

Claims

1. A method in a computing device for importing a customization of custom metadata elements of an application program, the method comprising:

receiving an indication of a name and a unique identifier of the imported custom metadata element of the application program;

when an existing custom metadata element of the application program has a name that is the same as the name of the imported custom metadata element and a unique identifier that is different from the unique identifier of the imported custom metadata element, changing the name of the existing custom metadata element; and

creating a new custom metadata element having the name and the unique identifier of the imported custom metadata element; and

when an existing custom metadata element of the application program has a name that is different from the name of the imported custom metadata element and a unique identifier that is the same as the unique identifier of the imported custom metadata element, changing the name of the existing custom metadata element to the name of the imported custom metadata element.

2. The method of claim 1 wherein the imported custom metadata element specifies a group with a group name and an area and when no existing group of the application has a group name and an area that is the same as the group name and the area of an imported custom metadata element, creating a new group with the group name and the area of the group of the imported custom metadata element.

3. The method of claim 2 including adding the imported custom metadata element to the top of the group.

4. The method of claim 1 wherein the receiving includes receiving a metadata for the imported custom metadata element name, unique identifier, type, format, and location.

5. The method of claim 4 wherein the metadata specifies the entity with which the imported custom metadata element is associated.

6. The method of claim 5 wherein the metadata is stored in accordance with an XML schema.

7. The method of claim 1 wherein when an existing custom metadata element of the application program has a name that is the same as the name of the imported custom metadata element and a unique identifier that is the same as the unique identifier of the imported custom metadata element, retaining the name and the unique identifier of the existing custom metadata element.

8. A method in a computing device for importing data for a customization of custom metadata elements of an application program, the method comprising:

receiving an indication of a name and a unique identifier of the imported custom metadata element of the application program;

when an existing custom metadata element of the application program has a name that is the same as the name of the imported custom metadata element and a unique identifier that is different from the unique identifier of the imported custom metadata element, creating a new custom metadata element having a name that is different from the name of the imported custom metadata element and a unique identifier that is the same as the unique identifier of the imported custom metadata element;

when an existing custom metadata element of the application program has a name that is different from the name of the imported custom metadata element and a unique identifier that is the same as the unique identifier of the imported custom metadata element, retaining the name of the existing custom metadata element; and

storing data in the custom metadata element with a unique identifier that is the same as the unique identifier of the imported custom metadata element.

9. The method of claim 8 wherein the imported custom metadata element specifies a group with a group name and an area and when an existing group of the application has a group name and an area that is not the same as the group name and the area of an existing custom metadata element, creating a new group with the group name and the area of the group of the imported custom metadata element.

10. The method of claim 9 including adding the imported custom metadata element to the bottom of the group.

11. The method of claim 8 wherein the receiving includes receiving a metadata for the imported custom metadata element name, unique identifier, type, format, and location.

12. The method of claim 11 wherein the metadata specifies the entity with which the imported custom metadata element is associated.

13. The method of claim 11 wherein the metadata is stored in accordance with an XML schema.

14. The method of claim 8 wherein when an existing custom metadata element of the application program has a name that is the same as the name of the imported custom metadata element and a unique identifier that is the same as the unique identifier of the imported custom metadata element, retaining the name and the unique identifier of the existing custom metadata element.

15. A computer-readable medium embedded with computer-executable instructions for controlling a computing device to resolve conflicts between names and unique identifiers of custom custom metadata elements of an application, by a method comprising:

receiving an indication of a name and a unique identifier of the imported custom metadata element of the application program;

when the imported custom metadata element without data is to be imported to the application program, resolving any conflict in favor of the imported custom metadata element; and

when the imported custom metadata element with data is to be imported to the application program, resolving any conflict in favor of an existing custom metadata element.

16. The computer-readable medium of claim 15 wherein the conflict is in names and wherein the resolving of a conflict in names in favor of the imported custom metadata element includes:

when an existing custom metadata element of the application program has a name that is the same as the name of the imported custom metadata element and a unique identifier that is different from the unique identifier of the imported custom metadata element, changing the name of the existing custom metadata element; and

creating a new custom metadata element having the name and the unique identifier of the imported custom metadata element.

17. The computer-readable medium of claim 15 wherein the conflict is in names and the resolving of a conflict in names in favor of an existing custom metadata element includes:

when an existing custom metadata element of the application program has a name that is the same as the name of the imported custom metadata element and a unique identifier that is different from the unique identifier of the imported custom metadata element, creating a new custom metadata element having a name that is different from the name of the imported custom metadata element and a unique identifier that is the same as the unique identifier of the imported custom metadata element.

18. The computer-readable medium of claim 15 wherein the conflict is in unique identifiers and the resolving of the conflict in unique identifiers in favor of the imported custom metadata element includes:

when an existing custom metadata element of the application program has a name that is different from the name of the imported custom metadata element and a unique identifier that is the same as the unique identifier of the imported custom metadata element, changing the name of the existing custom metadata element to the name of the imported custom metadata element.

19. The computer-readable medium of claim 15 wherein the conflict is in unique identifiers and the resolving of the conflict in unique identifiers in favor of an existing custom metadata element includes:

when an existing custom metadata element of the application program has a name that is different from the name of the imported custom metadata element and a unique identifier that is the same as the unique identifier of the imported custom metadata element, retaining the name of the existing custom metadata element.

20. The computer-readable medium of claim 15

wherein the resolving of the conflict in favor of the imported custom metadata element includes:

when an existing custom metadata element of the application program has a name that is the same as the name of the imported custom metadata element and a unique identifier that is different from the unique identifier of the imported custom metadata element,

changing the name of the existing custom metadata element; and

creating a new custom metadata element having the name and the unique identifier of the imported custom metadata element; and

when an existing custom metadata element of the application program has a name that is different from the name of the imported custom metadata element and a unique identifier that is the same as the unique identifier of the imported custom metadata element, changing the name of the existing custom metadata element to the name of the imported custom metadata element; and

wherein the resolving of the conflict in favor of an existing custom metadata element includes;

when an existing custom metadata element of the application program has a name that is the same as the name of the imported custom metadata element and a unique identifier that is different from the unique identifier of the imported custom metadata element, creating a new custom metadata element having a name that is different from the name of the imported custom metadata element and a unique identifier that is the same as the unique identifier of the imported custom metadata element; and

when an existing custom metadata element of the application program has a name that is different from the name of the imported custom metadata element and a unique identifier that is the same as the unique identifier of the imported custom metadata element, retaining the name of the existing custom metadata element.