Using an XML input file to update property values in bulk

When performing a complex update using the tc_attribute_bulk_update utility (updating many values on many properties throughout the database), use an XML input file to provide the query/update information with the -inputfileargument. The input file is a more efficient format for listing lengthy update instructions than using the command line arguments. You must use a combination of condition property name/property value pairs and update property name/property value pairs to: Query for the objects that satisfy the conditions specified through condition property name/property value pairs. Provide new values for the properties to be updated on the found objects. Structure the file as a series of UpdateSets entries. Each update set must contain type, condition, and update components. The following sample XML file illustrates the required sequence of the XML components, first type, then where, and then update. Copy Note There is no required sequence within the cond_prop component for the attrName, attrValue, and cond_operator components. Type component This component specifies the object type to be updated, such as item, dataset, or StructureContext. This component accepts only a single value. Condition components These components are placed in the section of the update set. They identify the property names and values to be queried. cond_prop cond_value cond_operator (optional) The cond_prop component specifies the internal name of the property to be queried for, as opposed to the display name. This component accepts multiple values in a comma-separated list. Each value must be a valid property on a Teamcenter object. For example: cond_prop=object_name,last_mod_date You can use multiple instances of this component, but it must always be paired with the cond_value component. The cond_value component specifies the current value of the property specified by the cond_prop component. This component accepts multiple values in a comma-separated list. Each value must be a valid property on a Teamcenter object. For example: cond_value=TextData_es_ES,"01-DEC-2011 00:00" You can use multiple instances of this component, but it must always be paired with the cond_prop component. You can use the cond_operator component to specify an operator to be used with the cond_prop and cond_value components. This component accepts the following values: = Equal != Not equal > Greater than >= Greater than and equal < Lesser than <= Lesser than and equal For example: Copy Update components These components identify the property names and values to be updated. update_prop update_value The update_prop component specifies the internal name of the property to be updated (as opposed to the display name), for example, object_desc, char VLA, and so on. This component accepts multiple values in a comma-separated list. Each value must be a valid property on a Teamcenter object. For example: update_prop=object_name,object_desc You can use multiple instances of this component. Each instance of this component should be paired with the update_value component. The update_value component specifies the new value for the property specified by the update_prop component. This argument accepts multiple values in a comma-separate list. For example: update_value=folder,"Home folder" You can use multiple instances of this component. Each instance of this component should be paired with the update_prop component. The input file supports the following persistent properties: Single-value properties Array properties Fixed length array Variable length array (VLA)