The App ID in the Applications segment is a unique identifier assigned to each application record for a part. PDM uses this ID to understand whether an imported application should update an existing record or be treated as a new application.
If a part has multiple applications, each application will have its own App ID.
For example, if a part has four application records, each of those records will have a different App ID. If you need to update one specific application, the App ID tells PDM which application record should be modified.
Why App ID is important
The App ID helps PDM match imported application data to an existing application record. When you export application data, make changes, and import the file again, the App ID is used to identify which existing application should be updated.
If the App ID is included, PDM will update the matching application record.
If the App ID is removed, PDM will treat the application as a new record and assign a new App ID.
This is important because removing the App ID when you only intended to update an existing application can create duplicate application records.
If you are adding new applications to an existing part number, do not reuse an App ID from an existing application unless you are trying to update that specific existing record.
A new application should generally be imported without an App ID so PDM can create a new application record.
If you use an existing App ID for a different application, PDM may attempt to update the original application instead of creating a new one.
Recommended testing
If you are unsure how App IDs will behave during import, we recommend testing with a sample or fake part number first.
You can:
Create a test part number.
Add a few applications in the UI.
Export the Applications segment.
Review the App IDs and Group IDs in the export.
Re-import the file with small changes while keeping the App IDs.
Test again by removing the App IDs to see how PDM creates new application records.
This can help you understand how PDM updates existing applications versus creating new records.
Best practices
Keep App IDs when updating existing applications: If you are modifying an existing application, keep the App ID in the import file so PDM can update the correct record.
Remove App IDs only when creating new records: If the application is completely new, leave the App ID blank so PDM can assign a new one.
Review Group IDs before importing: Group ID affects how applications are grouped into cards in PDM. Review this field before importing large application updates.
Export before making changes: Before importing application updates, export the current application data so you have a reference file with the existing App IDs and Group IDs.