PDXpert PLM Software
Keep system settings and remove test item records
Last update 2021-12-13
This is an advanced topic for PDXpert 9.0 and later. This removes all document, part, change form, and file attachment records from your database. You must have Windows administrator permissions, and be comfortable using SQL Server Management Studio to run the SQL queries.
As you design a new PDXpert system configuration, the best way to protect your work is:
Make a backup of the database with its current settings. Note the backup content for Step 5.
Set the new system rules and collection members for test.
Make a backup of the database with its new settings. Note the backup content for Step 5.
Test the new configuration with example items to confirm the settings are correct.
Items are parts, documents, change forms, and their item and revision file attachments.
Restore a database backup (without test data from Step 4).
If the test fails, restore the database backup from Step 1.
If test is successful, restore the database backup from Step 3.
If you want to make further settings changes, go to Step 2 and repeat.
If Steps 3 and 5 were skipped, use this procedure to recover a configuration that meets your needs, but without any test items.
Before you begin, back up your system. This procedure deletes documents, parts, change forms and files data. You cannot undo the changes it makes. If there's an error, or you don't like the results, then you must restore your backup.
Close the PDXpert Application Server after you back up the system.
All users must exit the system before starting this procedure.
This procedure deletes all file attachment records, except for those file records attached to Organization collection members.
If you've attached any external links or files to Organization collection members and you want to empty the \Library folder in Step 5, then use this query in SQL Server Management Studio to find all files attached to Organization collection members.
BOOrg.[Name] AS [Organization]
,PFile.[Name] AS [FileName]
,PFile.[FileId] AS [LibraryName]
INNER JOIN OrganizationFile OrgF ON OrgF.[Parent] = BOOrg.[Id]
INNER JOIN PhysicalFile PFile ON PFile.[Id] = OrgF.[PhysicalFile]
Using the results of this query, use one of these options:
- In the PDXpert client, use the Organization list to copy (if needed) each file attachment, and then delete it from the organization Files list. After you've deleted all files in Step 5, you can re-attach the saved files to their original organization records.
- In the PDXpert Server's \Library folder, use the LibraryName list to find and copy files into another folder. After you've deleted all files in Step 5, copy the saved files back into the \Library folder.
Test the complete process carefully before permanently deleting any data or files.
Open SQL Server Management Studio, connect to the PDXpertDB database, and run the following query:
-- Delete item records
DISABLE TRIGGER ALL ON [dbo].ChildItem;
DISABLE TRIGGER ALL ON [dbo].Item;
ENABLE TRIGGER ALL ON [dbo].Item;
ENABLE TRIGGER ALL ON [dbo].ChildItem;
--Delete PhysicalFile attached to items (not Organizations)
DELETE P FROM [dbo].PhysicalFile P
LEFT OUTER JOIN [dbo].OrganizationFile O ON O.PhysicalFile=P.Id
WHERE O.PhysicalFile IS NULL;
UPDATE [dbo].PDXpertInfo SET DatabaseId=newid();
Restart the PDXpert Server service or reboot Windows.
In the PDXpert client:
Select thecommand, then click the button (finishes instantly). Searching for items should not show any rows.
Review all system settings using the Next number values for identifier sequence members.command, as well as a reasonable sample of the collection members. If needed, reset the
Use the PDXpert Application Server to make a backup, so that you can restore this configuration later.
In Windows File Explorer, delete all files in the \Library folder only if no Organizations collection members have file attachments.
If you saved the member files before you started this procedure, you can now re-attach or copy the saved files.
This application note was relevant to the PDXpert software release that was current at time of publication. Product changes since that time may affect its utility. We'd be happy to assist you in assessing the applicability of this note to your situation.
Working within PDXpert
- Designing an engineering change process and workflow
- Server: Fast file content searches using IFilters
- Server: Scheduled backup for the database and library
- Server: Running several PDXpert Application Servers on the same network
- Batch Import: Preparing file attachments for import
- Batch Import: Converting a PDX package for PDXpert
- Batch Import: Keep settings, remove test item records
- Batch Import: Creating release sets for imported data
- Batch Import: Bulk replacing item attributes
- PDX package: Compare all product data, not just the BOM
- PDX package: IPC-2570 package implementation
- PDX package: IPC-2570 security signing and password extensions
- Adding a custom SQL Server report to PDXpert
- Adding a custom SQL Server report to PDXpert 8.0 to 11.2
- Designing email notice templates
- Including labor time and cost in assemblies
- Materials management for regulatory compliance
- Switching an existing item to a different type
- What's the difference between Item Revision State and Item Lifecycle Phase?
- Copying an assembly BOM to another assembly
- PDXpert permissions: User access design
Working with other software applications
- Using Altium Designer EDA software with the PDXpert client
- Using Altium Designer EDA software with the PDXpert server
- Using Cadence OrCAD Capture CIS with the PDXpert client
- Using Cadence OrCAD Capture CIS with the PDXpert server
- Using Pulsonix EDA software with the PDXpert server
- Importing a CAD bill of materials into PDXpert PLM software
- MRP/ERP data transfer options with PDXpert PLM software
- Exporting PDXpert PLM parts, BOM & sources to MRP/ERP
- Importing Trilogy Design Parts&Vendors data into PDXpert
- Exporting a bill of materials from PDXpert to Visio