Hi Stevie,
Your question is profound. The underlying context in your question is a reality check. The simple answer to your question is that data does not exist in Maximo by design. The query below contains the criteria used to create the LOCATIONUSERCUST. There is no data available in Maximo to meet the minimum criteria of your profound question.
SELECT * FROM ASSET WHERE location is not null and assetnum IN (SELECT ASSETNUM FROM assetlocusercust WHERE LOCATION IS NOT NULL AND addperson=0)
Consider a different interpretation of your question - I used Perplexity.ai to help provide a meaningful response.
Your question, "Has anyone created an object structure and MxLoader that will delete a personid from LOCATIONUSERCUST?" represents far more than a technical inquiry. It surfaces a data governance reality that demands global awareness across Technology and Organization Leadership responsible for enterprise asset management systems supporting mission-critical operations, regulatory compliance, and fiduciary accountability.
I hope the screenshot provides a visual context for your question.
MxLoader Capabilities Hidden in Your Question:
Bruno Portaluri, the visionary creator of MxLoader, developed the tool when data loading was the primary use case and REST API capabilities were in their infancy. Today's Maximo REST API offers comprehensive CRUD operations, enhanced authentication via API keys, robust validation enforcement, and standardized audit logging. The modern REST API architecture incorporates security controls and governance frameworks that reflect contemporary data governance requirements—capabilities that predate MxLoader's original design paradigm.
Bruno Portaluri released MxLoader in May 2014, as announced in his official blog post on May 15, 2014. His vision in designing MxLoader placed him more than a decade ahead of industry trends. Initially conceived as a tool for data loading operations, MxLoader operates through Object Structures, providing full CRUD (Create, Read, Update, Delete) capabilities. The reality your question mandates is that the times have caught up to Bruno's vision, more than a decade later.
To answer your question: Yes, deleting records via MxLoader is technically possible. Object Structures can be configured to support DELETE operations, and MxLoader can execute those deletions. However, this technical capability exists in tension with enterprise data governance principles, compliance mandates, and the embedded security controls that distinguish Maximo as an enterprise-grade asset management solution.
IBM Maximo powers global asset management operations across industries, where the consequences of data manipulation errors can extend beyond inconvenience to catastrophic outcomes.
The Reality Check We Must Face to Answer Your Question:
The ASSETLOCUSERCUST and LOCATIONUSERCUST views exist within a complex web of relationships that span assets, locations, persons, work orders, and compliance documentation. MxLoader's CRUD operations can create orphaned records, trigger validation failures in dependent processes, and compromise data integrity in ways that manifest gradually across interconnected business processes. MxLoader, while user-friendly, does not provide the relationship visualization or dependency analysis that would alert users to cascading consequences before execution.
Thanks for your question. Although deleting the custodian using MxLoader's LOCATIONUSERCUST is technically impossible by design. Your question is valid. Please see MxLoaders Data Manipulation Actions below.
