Integration Platform Technologies: Siebel Enterprise Application Integration > Creating and Maintaining Integration Objects > About Synchronizing Integration Objects >

Deleting a Component from the Integration Object

If you choose to deselect a component in the Synchronization wizard, then you specify to the wizard to delete the component in the integration object with the matching External Name Context property. The integration object that exists in the database has a component with the same External Name, External Name Sequence, and External Name Context as the unchecked component in the component selection tree.

In Figure 22, the Contact_Personal Address in the existing Account integration object is unchecked in the Synchronization wizard tree. This is represented by an X in this figure. Figure 22 illustrates this concept. Figure 23 shows the integration object after synchronization.

Figure 22. Deleting a Component from the Integration Object

Figure 23. Synchronization Resulting in a Deleted Component

The component Contact_Personal Address has been deleted. When you use the updated integration object, you cannot pass data for that component between a Siebel application and an external application. This example shows you how you might cause unexpected results by deselecting components. However, if you do want to delete a particular component from the integration object, then deleting a component from the integration object method accomplishes that goal.

Figure 24. Setting NoUpdate and NoDelete User Properties

Figure 25. Synchronizing the Integration Object with User Properties Set

Figure 26. Synchronized Integration Object with One Component Unchanged

Guidelines for Maintaining Integration Objects

As the examples illustrate, you must be aware of the possible changes that can occur when you synchronize business objects and integration objects. The Integration Objects Synchronize wizard can provide assistance in managing your integration objects, but you must have a clear understanding of your requirements, your data model, and the Siebel business object structure before undertaking a task as important as synchronization.

To make maintenance of integration objects easier, adhere to the following guidelines when creating or editing your integration objects:

• Use a meaningful name for any user key you have added that is different from the generated user keys. Using meaningful names helps with debugging.
• Inactivate user keys instead of deleting them.
• Inactivate fields instead of deleting them.