I have an issue when I click into a custom sub-object and then either click Return or Save & Return the sub-pages turn into tabs.
Below is the view of the master object's sub pages before I click into the sub-object:
Below is the master object view after I click Return or Save & Return:
This only occurs for only 1 sub-object, all other objects work normally.The problem seems to be that the Return and Save & Return button are adding '5204144.5204141' to the URL when it is not required.
Full URL after clicking Return:
If you remove the '5204144.5204141' from the URL, the page generated is as expected. As this is a system generated URL I cant modify it or re-create it.
I have done the following things to try and fix this problem:
The next course of action is to re-build the object but I prefer not to go down that path if I don't need to.
Anyone got any other idea's besides re-creating the object?
I think this will be a good situation for raising a support ticket, unless someone has hit this exact same thing before and had a general solution for it. If you could possibly include with that an Action Trace (aka Clarity sql trace) of your user performing this login, navigation, and problem when returning, that can help kickstart the investigation.
Conversely I'd like to be able to do this, sometimes a subpage also available as a tab would help the UX
I have seen this before on either version 13.0 or 13.3.
It happened sometimes when navigating (or clicking a direct link) deep into a structure of a subobject of a subobject of a subobject etc. and then either clicking return or back button (I cant remember which it was)
I don’t think we have the issue now on 14.2 patch 4.
CA Limited | Borupvang 5b | Ballerup | 2750
Mobile: +45 24 69 59 56 | Lennart.Johansson@ca.com
P Please consider the environment before printing this e-mail.
CA Software ApS is a company registered in Denmark under company registration number 75 13 76 13 with its registered office at the address set out above.
I wish it were possible to turn this on/off, it would be good to have conditional tabs
I did a bit more digging and I think I found the lines in the database that could be culprits. In the CMN_ACTIONS table there are 2 rows that are not in other replica environments.
The rows are inactive so I am not sure why CA PPM is using these actions. I prefer to remove these rows via PPM. Does any one know how? I could not find these in the object.
Found the problem and solution.
The problem was in the administrator (Principal_ID=1) had saved Favorites referencing removed custom object instances. Once I deleted all the favorites in the the My Links area the problem disappeared.
I think there is a bad query in PPM somewhere as PPM was using inactive user actions (Favorites). These actions were user based and inactive and should not have been referenced at all.
I just did a quick test on this with 14.3 and wasn't able to reproduce this on that description alone - am I missing any crucial step or getting any slightly wrong? If not, then what is the exact patch and version number you were getting this with please:
1. Create new custom object
2. Edit the default page layout of your custom object and add a new tab, put the DHL portlet on it.
3. Create new custom subobject with first object as parent
4. Create 3 instances of master object
5. Create subobject instances under first master instance.
6. Create subobject instances under third master instance.
7. Create favorite entries for the first and second master instance property views.
8. Delete the first master instance.
9. In the third instance, navigate to any subobject instance properties and then click Save and Return.
10. Delete the second master instance.
11. In the third instance, navigate to any subobject instance properties and then click Save and Return.
After steps 9 and 11 I was hoping to reproduce your issue but it didn't. Would you mind clarifying? If this can be reproduced in current versions (i.e. it hasn't yet been fixed) I would want to get this reported. If it cannot be reproduced on current versions, I'd like to be able to figure out when/where it was fixed.
This problem occurred in 184.108.40.2066 09 3.I tried to replicate this problem by adding to favorites and removing the custom instance but it didn't work. There must be another aspect to this issue.