Rebase On Grandchild Workspace Overrides Existing Change Without Reporting Conflict (Doc ID 3037009.1)

Last updated on JULY 26, 2024

Applies to:

Symptoms

With the following steps, script written in grandchild workspace will be lost without reporting conflict.

1. Login to Siebel Tools.
2. Create an integration workspace under MAIN (int_child)
3. Create an integration workspace under int_child (int_grandchild)
4. Create a developer workspace under int_grandchild and add a script in BusComp_PreSetFieldValue for Contact BC.
5. Deliver the change to int_grandchild. (Contact BC has the script created at the step4)
6. Create a developer workspace under int_child and change 'No Delete' to TRUE for 'SIS Account List Applet'.
7. Deliver the change to int_child.
8. Create a developer workspace under MAIN and add a different script in BusComp_PreSetFieldValue for Contact BC and set 'No Insert' to TRUE for 'SIS Account List Applet'.
9. Deliver the change to MAIN.
10. Open int_child. Run a rebase with MAIN. Now int_child has the script created at the step8 and also 'No Delete' and 'No Insert' are TRUE for 'SIS Account List Applet'.
11. Open int_grandchild. Run a rebase with int_child. Here, we should see the conflict between the script created at the step4 and step8. But there is no conflict displayed.
12. If you finish the rebase, the script created at the step4 is gone. There is no way to save it. You see only the script created at the step8.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.