Thanks for the info! The issue was with moving locations that were under a parent - I was trying to move them to a different parent at a different hierarchy level. At first, I tried doing it manually by opening each location and changing the parent field directly. That seemed to work at first - the location appeared under the new parent - but it also started showing up at the top level of the hierarchy, which wasn't expected. It looked like the location was showing in two places, and I'm not sure how to explain that better π
Thanks to @Juris Flugins for pointing me to More Actions > Move Locations (or something like that) - that worked better, but even then, only some of the locations were moved, and others didn't move at all.
------------------------------
Arturs G
------------------------------
Original Message:
Sent: Wed April 30, 2025 12:44 PM
From: LAXMI SAI SINDHU ATLURI
Subject: Issues Moving Locations and Assets in Treeview in IBM Maximo
Hi Arturs G
I could not understand your question completely. but if you want to make sure hierarchy for locations, there is a table called LOCANCESTOR.
This table will have entries of the location till it's top level along with the entry of it's own. As shown in the picture if you have 3 levels of locations, the entries in LOCANCESTOR table will be as shown.
------------------------------
LAXMI SAI SINDHU ATLURI
Original Message:
Sent: Wed April 23, 2025 04:56 AM
From: Arturs G
Subject: Issues Moving Locations and Assets in Treeview in IBM Maximo
Hello Maximo Community,
I'm currently facing an issue when trying to move a location and its associated assets in the treeview. Specifically, I'm trying to move 5 (five) items (a location and the assets underneath it) to a different location. 3 (three) of the items moved successfully, but 2 (two) of them behave strangely. They appear to move to the correct parent location, but they also show up at the top-level of the treeview as if they have no parent.
In the Location application, I've already updated the parent for both the location and assets, and everything looks fine in the app itself. However, the issue persists in the treeview where the assets seem to still be registered at the top level.
I've checked the parent-child relationships in the LOCHIERARCHY table and LOCATIONS table, and they appear to be set correctly.
My question is: Is there anything else I should be checking or any hidden relationships or constraints that could be causing this behavior? For example, could there be asset-specific or location-specific data that's preventing the proper movement in the treeview?
Any insights or suggestions would be greatly appreciated!
Thank you!
------------------------------
Arturs G
------------------------------