Data wizard limitations
The data wizard updates records only if the status of the parent record is set to Enabled. For example, you cannot update a company if the company is set to Offline on the Company form.
This topic provides the following information:
The data wizard does not update the following areas:
Any character fields that contain the target value concatenated with other text. For example, if you are updating the Company Name from "My Company" to "Calbro," instances of "My Company" in Work Info fields and Summary fields would not be updated. Only instances of "My Company" in the Company Namefield would be updated.
Note
Modifications to a group name using the data wizard also require a manual modification to any concatenated field values on the Group form. For example, if you are changing a group name, you must open the Group form and change the long group name to the new value. If you do not change the long group name, email notifications might not work correctly.
- Qualifications on the Report Console or notification messages.
- Additionally, you cannot use the data wizard to change your own Login ID.
Oracle database limitation
When the data wizard is used for an Oracle database, it cannot update data that has leading or trailing spaces.
Limitations of auditing
The audit log file is not updated when you run the data wizard. The only information available on a form to track what changes the data wizard has made is the name captured in the Last Modified By field and the date captured in the Last Modified Date field of a form. However, if a form is further updated after it has been modified by the data wizard, the record of who ran the data wizard on the particular form is lost.
Updating Login ID
The Submitter field on BMC Remedy ITSM application forms and on CI forms is populated with the applicable Login ID value. When you change a Login ID, the Submitter field is updated on all applicable BMC Remedy ITSM application forms.
If the Last Modified By field is the target value, the data wizard does not set the field to the new value. When the data wizard makes updates, it sets the Last Modified By field to the Login ID of the person making the update.
Updating categorization
The product catalog, operational catalog, and generic catalog include multiple levels of categorization. Catalog entries can be defined to multiple levels of categorization.
The following table defines the levels of categorization.
Examples of product catalog entries
Categorization level |
Example 1 |
Example 2 |
Example 3 |
|---|---|---|---|
Tier 1 |
Hardware |
Hardware |
Hardware |
Tier 2 |
Machine |
Machine |
Machine |
Tier 3 |
Server |
Server |
|
Manufacturer |
Hewlett Packard |
||
Product Name |
Proliant |
The following three scenarios illustrate how the levels of categorization that are present in your catalog and the levels of categorization that you specify in the data wizard affect which categorization records are updated:
- Scenario 1 — All three examples are present in your product catalog, and you want to change "Machine" to "Processing Unit." You could specify only the first two tiers to be updated. The remaining categorization levels are updated throughout the catalog.
- Scenario 2 — All three examples are present in your product catalog, and you specify three tiers to be updated (for example, you change Hardware - Machine - Server to Hardware - Processing Unit - Server). Example 1 and Example 2 are both updated, but Example 3 is not updated.
- Scenario 3 — Example 3 is not part of the product catalog, and you specify three tiers to be updated. Any forms outside the product catalog with only two tiers specified (for example, an incident with product categorization of Hardware - Machine) are updated, however, to keep categorization consistent. These additional forms that are updated are not included in the count. As a result, if you compare the audit for the count and the update, you might notice a discrepancy.
Updates to the product catalog, operational catalog, and generic catalog work the same way.
The data wizard has a limitation on updating categorization. For example, the product catalog could have two entries with the first entry containing the following tiers:
- Tier 1 — Hardware
- Tier 2 — Processing Unit
- Tier 3 — Desktop
The second entry could contain the following tiers:
- Tier 1 — Discovered
- Tier 2 — Machine
- Tier 3 — Server
If you specify in the data wizard to change Tier 1-Discovered to Tier 1-Hardware and to change Tier 2-Machine to Tier 2-Processing Unit, the update is not allowed because Tier 1 and Tier 2 already exist as Tier 1-Hardware and Tier 2-Processing Unit. Instead, you would specify additional tiers when you update categorization. In this example, you would also specify to change Tier 3-Server to Tier 3 -Server. Although the value remains the same for Tier 3, because the values change for Tier 1 and Tier 2, the updated product catalog entry is not the same as the original product catalog entry.
Note
Before you run the data wizard, you must follow the instructions in Prerequisites to updating target values using the data wizard.
Comments
Here is a little script to check if you have some inconsistencies in the "Support Group" - "Group" combination. And an update to repair it. Maybe BMC can have a look at it and confirm the correct work of this.
Just for SQL Server not Oracle!! ( In Oracle you should make the concat operator to || in the select statement )
Hope that helps...
-- Check wrong groups
SELECT
sg.Support_Group_ID,
sg.company + '->' + sg.Support_Organization + '->' + sg.Support_Group_Name AS
"Correct_Long_Group_Name",
g.Long_Group_Name,
g.group_id
FROM
ctm_support_group sg
INNER JOIN
CTM_SYS_Access_Permission_Grps a
ON
sg.Support_Group_ID = a.Support_Group_ID
INNER JOIN
group_x g
ON
a.Permission_Group_ID = g.Group_ID
WHERE
sg.company + '->' + sg.Support_Organization + '->' + sg.Support_Group_Name != g.Long_Group_Name;
-- Update values
WITH
wronggroups AS
(
SELECT
sg.Support_Group_ID,
sg.company + '->' + sg.Support_Organization + '->' + sg.Support_Group_Name AS
"Correct_Long_Group_Name",
g.Long_Group_Name,
g.group_id
FROM
ctm_support_group sg
INNER JOIN
CTM_SYS_Access_Permission_Grps a
ON
sg.Support_Group_ID = a.Support_Group_ID
INNER JOIN
group_x g
ON
a.Permission_Group_ID = g.Group_ID
WHERE
sg.company + '->' + sg.Support_Organization + '->' + sg.Support_Group_Name !=
g.Long_Group_Name
)
UPDATE wronggroups SET Long_Group_Name = Correct_Long_Group_Name;
Hi Matthias,
Thank you for your comment. I will confirm with the SME and update the content.
Regards,
Mokshada
Log in or register to comment.