Query itself can’t, unless you’re referring to finding items with Where-Used-One-Level-Latest-Rev search (but that’s bottom up instead of top down like what you’re asking for).  Use Query to find items and get an array list of item numbers though it’s up to a different part of the script to extract first level BOM.  Does that make sense?

Oh, nevermind.  There’s 584 database tables in Agile – too many to list here.  I got the list by using.  
statement = connection.prepareStatement(“SELECT table_name FROM user_tab_cols”);

Well, names (usernames, that is) and oftentimes job titles aren’t considered PII, unless the EGDPR as you mentioned is considering it personal data.  If compliance is that strict, do an import to update or nullify those selected data fields for inactive users.  You could also develop a script to do just that for future user inactivations.  
Username is not PII, so there shouldn’t be an issue with keeping that as is in your system.  If you have to update the other fields, you can do so – Agile will need something in the First Name and Last Name fields, though it doesn’t have to be a person’s full name.

Check your “Upload File Size Limit (in MB)” settings (Admin -> System Settings -> Viewers and Files).  If it’s set to zero, you have no limit and Agile will let you upload your 7GB file.  As long as the back end server itself isn’t full, you should be fine.

It’s complicated, but doable.  Write a script that gets the original manufacturing object like so:

IEventInfo req = obj.getPXEventInfo();
IObjectEventInfo objectEventInfo = (IObjectEventInfo)req;
IDataObject originalmfrpart = objectEventInfo.getDataObject()
String newNumber = obj.getNewNumber()  //this is thew new part number
String manufacturer = originalmfrpart.getValue(1647) //gets the old Manufacturer

Then use the manufacturer of the old item to load the new Manufacturing object.
Note, this won’t work (returns a null object) if you change manufacturer on the save as.  There, write a separate method to fetch the value from the history tab of the old object like karthik mentioned above (I used some clever use of tokenize and getAt).

Here’s how to also check on the status of your file manager:
http://[your filemanager ULR and port]/Filemgr/Configuration
(get your URL from the System Locations settings on the Agile Admin tab)
If that link doesn’t work for you at all, as I’ve found, the File Manager server is down and needs a reboot.  Other than that, it should say “Success” in the charts.

Hi Scott,
Oh weird.  At my old company, which used 9.3.4., I could have sworn I remember the User Login Failure Report showing failed log-in attempts .  Here at my new company, which is using 9.3.3., the Login Failure Report only shows invalid approval passwords and attempts to log-in using invalid account.  This must have been fixed in the later versions of Agile, I suppose, but I’m not familiar enough to know the exact answer for you.  I figure there’s database SQL searches that’s doable too.

I’ve been dealing with the same thing today.  Try using Common Constants:
mfrPart.setValue(CommonConstants.ATT_PAGE_TWO_TEXT01, “newvalue”)

I typically just log-out, log-back in whenever I get that error and it’s fixed.  Not sure the cause – seems pretty random.  
Second step is to reset the application server if it’s a repeated problem.

Try some of the administrator reports.  Have you tried using either the User Login Failure Report, User Usage Report, or User History reports?