PDXpert 9.3 release notes (change history)
Published updates in the PDXpert 9.3 series software (all dates are UTC).
◄ PDXpert 9.2 • PDXpert 10.0 ►
Before upgrading: Read all release notes published from your current release to this new release.
PDXpert 9.3 requires SQL Server 2008 or later. If your PDXpert system currently uses SQL Server 2005, refer to the SQL Server upgrade instructions before installing this release.
Microsoft's technical support for Windows XP, Server 2003 and Vista has expired. These products are no longer included in our compatibility testing. PDXpert system requirements identify supported replacements for these products.
9.3.27514.548: 2014-07-22
-
New default analyst can be defined in Change Forms collection member. See help topic Collections reference > Changes > Change forms > Attributes tab. [B866]
-
New Data Transformations collection syntax defines parameterized SQL query for individual item selection in Report/Export Wizard. See help topic Collections reference > General > Data transformations. [C27355 et seq]
-
New F5 key) reloads active item record from database. [B8190]
menu command ( -
Update CollectionPersons.csv import file to create user accounts. [B9194]
-
Update External Data Importer to block CollectionPersons.csv import where it finds more than one matching Persons record. [C27293]
-
Update UOM Categories collection to permit only one Unconvertible UOM category. Removed classification status checkboxes from UOM Categories form. [B9195]
Upgrade effect: Any units of measure that aren't convertible are moved to the standard Unconvertible category, and all other non-convertible UOM categories are deleted.
-
Update system requirements to use .NET Framework 4.5.1 (down from 4.5.2). [C27492]
-
Fix PDX package export from change form. [B9196/C27514]
-
Fix re-indexing to reset FileIndexQueue. [C27340]
-
Fix part's Default unit of measure filter to apply UOM Categories setting Use on part. [C27382]
9.3.27522.550: 2014-07-25
Update database schema to optimize performance running "inverted BOM" report. [C27522]
Fix case where canceled revision's BOM, References or Sources are duplicated on the second revision of a subsequent re-release. [C27520]
9.3.27590.551: 2014-08-18
New "Denver DB" (a Berkeley DB distribution for Windows) provides a multi-access database upgrade to Altium users. A poorly-behaved ODBC application may assert exclusive control of the client-side SQLite DB file, and maintain a file lock after completing a query. This behavior prevents the PDXpert client from updating the SQLite database. To work around this issue, upgrade PDXpert's standard SQLite DB to Denver DB. [C27554]
To work around this issue, upgrade PDXpert's standard SQLite to SQL Server LocalDB (PDXpert 9.3.27875.554 and later).
Update Preferences window to allow read-only users to unlock form. [B9192]
9.3.27676.552: 2014-08-26
Update eliminates user confirmation when downloading new client release from updated server. [C27670]
Upgrade effect: PDXpert clients prior to 9.3.27676.522 will continue to request confirmation before upgrading. The PDXpert client 9.3.27676.522 (or later) will not request confirmation. Therefore, switching between a pre-9.3.27676.522 server and post-9.3.27676.522 server will request confirmation half the time.
Update removes obsolete Change cannot be approved if an affected item has a rule violation checkbox from Change Forms member form. [C27600]
Update removes obsolete BOM type is for documents checkbox from BOM Type Codes member form. [C27624]
Fix BOM context menu function Find (not ChildNumber) column and only the imported part number is changed. [C27674]
to add/remove a row in the case where the comparison anchor is the
9.3.27804.553: 2014-09-11
-
Fix change form PDX package export where Trustee is not Originator. [C27802]
9.3.27813.553: 2014-09-15
-
Fix client error when a member of the Identifier Sequences collection is opened. [B9207]
9.3.27875.554: 2014-09-30
-
New SQL Server LocalDB support provides a multi-access database upgrade to Altium users. This is the preferred upgrade of the SQLite local views database.
A poorly-behaved ODBC application may assert exclusive control of the client-side SQLite DB file, and maintain a file lock after completing a query. This behavior prevents the PDXpert client from updating the SQLite database.
LocalDB ensures that an ODBC application (e.g., Altium Designer) can't block updates to the local views file. Configure in the Preferences window: Enable local views: Using SQL Server LocalDB. [C27832]
-
Update BOM, Sources and References lists to display very long item numbers (about 24 numeric characters) and longer BOM component descriptions. [B9198]
-
Update External Data Importer ItemMaster.csv export of custom attributes to be uniquely identified by Name, rather than by Scheme and Name. Previously, custom attribute values on different item types were merged into the one public view column if they shared the same name and scheme (e.g., collection, date, Boolean). In this release, custom attribute vales are merged even when the schemes are different. [C27838]
-
Fix Sources and References lists to display item icons. [B946]
-
Fix client log-in error Exception has been thrown by the target of an invocation when switching between application servers of different 9.x releases. [B9209]
- 001. Installation overview
- 002. Preparing the server computer
- 003. Standard PDXpert System setup
- 004. Standard PDXpert PLM client setup
- 005. Installing LocalDB for PDXpert client ODBC
- 006. Custom installation: SQL Server
- 007. Custom installation: PDXpert server
- 008. Custom installation: Private cloud
- 009. Custom installation: Client deployment
- 010. Upgrading the PDXpert Application Server
- 011. Upgrading the PDXpert PLM client
- 012. PDXpert server post-install checklist
- 013. Install license CA certificate chain
- 014. Moving PDXpert server database and files
- 015. Managing a PDXpert test server
- 016. PDXpert Application Server diagnostics
- 017. PDXpert PLM client diagnostics
- 018. Microsoft SQL Server diagnostics
- 019. Microsoft SQL Server log files
- 020. Connecting SQL Server Management Studio
- 021. Upgrading SQL Server
- 022. Service configuration settings
- 023. Application folders and files
- 024. System architectural diagram
- 025. Release notes (change history)