Community Tip - Learn all about the Community Ranking System, a fun gamification element of the PTC Community. X
Version: Windchill 12.1
Use Case: This idea is to help prevent the bad practice of letting files sit with upload errors without attention for long periods of time (weeks/months/etc.) This report would be able to capture all files within Windchill that have upload or other related errors, so the support team can work with those users proactively instead of reactively when something is broken or lost at a bad time.
Description:
We had a scenario where a user had some check-in errors from almost a year ago on some files and didn't address them then like they should've. Since so much time had passed, the user may have deleted something referenced as well as some file name conflict issues that were present. It was a mess in the moment for many reasons but seemed like a valuable opportunity to see if we can be proactive for other users/errors that exist. All-in-all, if we had a report to catch all upload errors
Fields to capture: User, FileName, UploadDate, ErrorStatus, Size, Revision.
Solved! Go to Solution.
I had a similar issue, but a different approach. I made a report to query New Objects in Workspaces that hadn't been checked in. The report is a little more complex than probably needed because it returns both WTParts and CAD files. The report has a parameter so you can choose to only return items that have been sitting for over X days.
Here's what the tables and joins look like:
Select or Constrain:
And then Criteria:
The Or condition has 2 sub-selects. It's been so long since I made this, I don't actually remember why this works. The first one is for returning CAD:
The 2nd is highly similar, but for the WTParts:
In practice though, what I've found is that engineers have a ton of abandoned files, and they don't like to clean up after themselves. I've stopped using the report entirely
I had a similar issue, but a different approach. I made a report to query New Objects in Workspaces that hadn't been checked in. The report is a little more complex than probably needed because it returns both WTParts and CAD files. The report has a parameter so you can choose to only return items that have been sitting for over X days.
Here's what the tables and joins look like:
Select or Constrain:
And then Criteria:
The Or condition has 2 sub-selects. It's been so long since I made this, I don't actually remember why this works. The first one is for returning CAD:
The 2nd is highly similar, but for the WTParts:
In practice though, what I've found is that engineers have a ton of abandoned files, and they don't like to clean up after themselves. I've stopped using the report entirely
Hi Joe, great explanation and detail! Thank you so much! This seems like a great idea and I will be sure to test/report back asap.
Cheers!