> For the complete documentation index, see [llms.txt](https://help.auxalia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.auxalia.com/plant-tools/plantreporter/release-notes.md).
# Release Notes
### Systems Requirements
#### OPERATING SYSTEM
* Windows XP - Windows 11
#### AUTOCAD®
* AutoCAD® Plant 3D 2022 - 2027
### History
#### Version 10.2.0.5321 (07.09.2026)
New: Creating Data Views in PlantDataManager and PlantReporter (PT-2325)
New Data Views in PlantDataManager and PlantReporter. Define a custom grid view in Plant Project Setup (new Queries node) by selecting classes and exactly the properties you need — similar to a PlantReporter query — including combining properties from different classes into a single, freely-named column. In PDM the view appears under Project Queries in the Views list; in PR it can be selected as the query for a report configuration.
New: New command line parameter /PRINT to create the version or revision and print in one run (PT-5574)
Command line: /PRINT creates the version or revision and prints the report in a single run, so the exported file name carries the new number.
New: Query configuration options to return objects existing in multiple drawings only once (PT-5632)
PlantReporter: The query configuration can now return objects that exist in several drawings only once, instead of one row per drawing. Two independent options cover pipe line groups and signal line groups on one side and all other objects on the other, each with its own drawing-number delimiter.
Change: PDM, PDM Plugin, PR and PET must ignore data cache files that are not registered in the Misc project part (PT-5577)
PlantDataManager, the PlantDataManager Plugin, PlantReporter and PlantExpressTools now only use data cache files that belong to the project. A data cache file that was merely copied into the project's data cache folder is ignored, and PlantDataManager warns you that it found one. Use Import Data Cache in PlantDataManager to take such a file into the project.
Bug fix: Reports with scripts fail with "Cannot execute report scripts because the application does not include required libraries" (PT-5524)
Reports containing scripts can be previewed and printed again in PlantReporter and PlantDataManager.
Bug fix: Creating a version/revision fails with "no such column" after a new Revision Field is added (PT-5561)
Adding a new property under Revision Fields no longer breaks the creation of versions and revisions. The new field is added to the revisions database with the next version or revision that is created.
Bug fix: Zip migration loses config files when PlantTools.zip already exists: added files are discarded by an undo check-out and the loose files are deleted (PT-5622)
Configuration files that are added to a project after its PlantTools.zip was created are now migrated into the zip correctly. Previously they were removed from the project without being stored in the zip, so their content was lost. The first migration of a project was never affected.
Bug fix: Newly added Revision Fields break creating and editing versions/revisions until the project is reopened (PT-5651)
A revision property added under Version/Revision > Revision Fields is now available as soon as the Plant Project Setup is confirmed with OK, in a Collaboration or Vault project as well. Creating, exporting and editing versions and revisions used to fail with "no such column" afterwards, and the new property stayed out of the revision table. Existing versions and revisions can be filled in for the new property in the PlantReporter Reports tab.
Bug fix: ACProject.db stays checked out when PlantReporter does not close normally (PT-5656)
Fixed: the revisions database (ACProject.db) could remain checked out in cloud and Vault projects.
Bug fix: PlantReporter writes the report files to "../ReportFiles" inside PlantTools.zip, outside the archive root (PT-5722)
PlantReporter stored a project's report configuration files (.rcf and layout) in a hidden location inside PlantTools.zip that Windows File Explorer could not show. Affected projects are corrected automatically the next time they are opened in PlantReporter; the report configurations themselves are unchanged.
Bug fix: PR/PET: switching projects adds the new project's revision fields as columns to the previous project's ReportRevisions table (PT-5732)
PlantReporter and PlantExpressTools no longer copy the revision fields of one project into the versions/revisions database of a previously opened project when switching projects. Projects that were already affected can be repaired with the clean-up dialog that appears on open.
#### Version 10.1.0.5150 (28.07.2026)
New: Remove dependency on AutoCAD version setting (PT-2281)
Groundwork toward removing the AutoCAD-version dependency: the new hardened assembly resolver is host-aware, detecting whether it runs inside AutoCAD or as a standalone PDM/PR/PB exe and applying different rules accordingly.
New: PR: Name the class/property that exceeds the 64-character query limit (replace generic error dialog #00732) (PT-2441)
Due to limitations in the Plant 3D API the length of the class + '.' + property combination must not exceed the 64-character limit. Instead we show a dialog with the specific information, so you can correct the project setup directly.
New: Revision is Master option for Report Revisions (PT-3361)
PlantReporter can use the option **Revision is Master** too now. Before it was only available in PlantProjectManager. When creating a new Revision the Version will be set to the value set in **First Version** in the settings.
New: Reorganize ACPlant 202* (PT-4215)
Groundwork for the ACPlant 202\* reorganization: PlantTools now uses a single shared, version- and host-aware assembly resolver with a defined Libraries (NetCore/FrameWork/) layout, replacing the per-host greedy resolvers.
New: Extend Version/Revision with Custom Properties (PT-4657)
You can add custom properties for versions/revisions.
New: Add a project number variable for the "Export file path" (PT-4665)
\[PNO] variable for the project number in the Export file path.
New: Extend _prePrintForm to allow editing property data (PT-5065)
Added version/revision properties in Pre-Print form to edit version/revision properties before creating version/revision.
New: Versioning of drawings and folder based reports (PT-5164)
Support to create versions/revisions for drawings and folders.
New: Adapt selected Export file path when selecting a folder within the proejct (PT-5277)
The Export file path folder-browse now stores the selected folder relative to a variable (\[DC] / \[PP]/\[PN] / %ENV%) instead of an absolute path.
New: Command Line Parameters to create versions/revisions and compare (PT-5408)
Support of additional Command Line Arguments to automate the creation of versions/revisions and compare for reports.
New: Report config files (.rcf/layout/collection.xml) not copied into project when PlantReporter.xml migrates with location = Project (PT-5413)
Fixed: when the PlantReporter settings are migrated to the project and the report files location is set to "Project", the existing report configurations (RCF and layout files and the collection) are now copied into the project if it does not yet contain any.
New: Show which files/folder are handled during the migration process in PR/PDM and the AutoCAD plugins (PET, PL, PSD) (PT-5414)
PlantReporter, PlantDataManager and the AutoCAD plugins (PlantExpressTools, PlantLink and PlantSpecDriven) now show progress during the PlantTools.zip migration of collaboration projects: the wait dialog displays the current step and the file or folder currently being processed, instead of appearing to hang.
New: Migration: remove leftover backup files and empty folders from ACPlantTools (PT-5417)
Migrating a project to PlantTools.zip now also removes leftover backup files (.bak) and the empty folders left behind, so the ACPlantTools folder no longer keeps obsolete files and folders that prevented it from being deleted. Already-migrated projects are cleaned up automatically the next time they are opened.
New: A new variable for the folder name is available (PT-5420)
You can use the folder name for the path or file name of your output file in PlantReporter.
New: Importing a report configuration prompts before overwriting an existing one (PT-5425)
When importing a report configuration that already exists, PlantReporter now asks whether to overwrite it instead of silently replacing or skipping it. This works for both project-stored (BIM/ACC and local) and general (on-disk) report files.
New: Full redesign of PlantReporter's main user interface (PT-5426)
The user interface of PlantReporter was aligned with PlantBatch. You can also search and filter the drawing tree and use collapse/expand in the context menu.
New: Show resolved export file path as Target (PT-5427)
The "Target" field in the PlantReporter main form now shows the resolved export file path from the report configuration instead of just the file type. Variables that cannot yet be determined before printing (e.g. drawing name, revision) remain visible as placeholders; date and time use the current timestamp.
New: Performance improvements when creating reports (PT-5428)
Major performance improvements when creating and exporting reports, especially for large 3D projects and revision-enabled reports. The version/revision dialog opens quickly, the report-data query is much faster, creating a version/revision is dramatically faster (data is appended rather than rewritten), and comparing two versions is much faster. The data read to open the dialog is now reused for the export instead of being read again, and long operations show a progress dialog. These query improvements also speed up reports in PlantDataManager.
New: Show dialog to copy report configurations when opening a project if no report configurations are available (PT-5432)
When you open a project whose report-configuration location (Project or Custom) has no report configurations yet, PlantReporter now asks before copying them from the General location, instead of copying silently.
New: PR: Add "Run Refresh directly before Export/Print" setting to skip redundant cloud refresh (PT-5437)
Added a new setting "Run Refresh directly before Export/Print" (enabled by default) that lets you skip the automatic project refresh before printing or exporting collaboration projects, avoiding a redundant refresh when the project was already refreshed on load.
New: Auto-size Export Results dialog to fit the full file path width (max 1000 px) (PT-5438)
The Export Results dialog now resizes to show the full length of exported file paths without a horizontal scrollbar (up to a maximum width), making the results easier to read.
New: Desktop Connector variable for the Export file path (PT-5448)
Variable for the Autodesk Desktop Connector path in the Export file path.
New: Windows path variables (environment variables & shell folders) for the Export file path (PT-5449)
Use common Windows locations (environment variables and shell folders) as the Export file path root.
New: Reports tab to view and edit report versions/revisions (PT-5472)
PlantReporter now offers a Reports tab (shown when versioning is enabled) that lists every report having versions or revisions, grouped by type (P\&ID, 3D, Drawings), and lets you view and edit their version/revision details directly.
New: Show find panel and hide group panel on Revisions and Work History tabs in PlantProjectManager (PT-5473)
The Revisions and Work History tabs of the Plant Project Manager now provide an always-visible search field, matching the Properties tab, and no longer display the column grouping panel.
New: Option to download all PlantTools files (PlantTools.zip + ACPlantTools/MISC files) for Vault/Collaboration projects (PT-5496)
PlantBatch can now optionally download all PlantTools files - PlantTools.zip and the ACPlantTools/MISC files such as ACProject.db, plus databases referenced by .udl files - after opening a Vault or Collaboration project from the command line. Enable it via the new 'Download PlantTools files when using Vault/Collaboration Projects' option in PlantBatch Settings (off by default).
New: Migrate legacy loose "ReportFiles" folder into PlantTools.zip on project open (PT-5499)
PlantReporter now migrates report configuration and layout files from the old loose "ReportFiles" project folder into PlantTools.zip automatically when the project is opened, with a prompt to resolve duplicates.
New: New command line parameter /FOLDER to select project folders (PT-5519)
PlantReporter now supports the new command line parameter /FOLDER. Like /DWG it accepts a single project folder or a comma-separated list of folders - given as a path inside the project tree.
Change: Remove 'One report' as an Output Type option (PT-5163)
The One report options was removed from the Output Type selection since it was only used for project groups which are not supported anymore and were removed long time ago.
Change: Removed Progress Form when generating report output (Export, Preview, Compare versions) (PT-5435)
The "Exporting x of N documents" progress dialog that briefly appeared when printing or exporting a report, previewing it, or comparing report versions has been removed. The export result window (or the preview) shows the outcome.
Change: Slim PET/PR/PB installer payload - ship minimal per-year Autodesk runtime (PT-5501)
Smaller PlantExpressTools, PlantReporter and PlantBatch installer downloads (reduced bundled runtime payload).
Change: Migrate PlantTools help links to the new help.auxalia.com documentation (PT-5506)
The in-application help (F1 and the ? buttons) now opens the new online documentation at help.auxalia.com.
Bug fix: Tables in ACProject for storing version/revision data are not created for dbo (PT-1052)
Fixed errors when working with versions and revisions on SQL Server projects where tables were created in the wrong database schema instead of dbo.
Bug fix: Proxy Settings and Auto Update are reset when switching the language or navigating between settings pages (PT-4404)
Fixed an issue in the Plant Project Setup where the Proxy and Auto Update settings were reset before saving when switching the language or navigating between settings pages.
Bug fix: PlantReporter throws ArgumentNullException when creating a report with Version/Revision (PT-5280)
Fixed an error that prevented creating a report with a Version or Revision in PlantReporter. On Plant 3D 2027 / cloud collaboration projects, report creation failed with "Value cannot be null. (Parameter 'connection')". The revision record is now written correctly and the report is created with the selected Version/Revision.
Bug fix: PlantReporter Settings: 'Access denied' to PlantTools.zip when saving (Versions/Revisions tab) (PT-5411)
Fixed an error that prevented PlantReporter settings (for example on the Versions/Revisions tab) from being saved when the project configuration is stored in PlantTools.zip.
Bug fix: PlantReporter Settings: switching report files location to General is not saved (PT-5412)
Fixed the PlantReporter report-files location setting not being saved when switching it to 'General'.
Bug fix: Deleting or importing a report configuration has no effect on BIM/ACC (cloud) projects (PT-5423)
Fixed an issue where deleting or importing a report configuration had no effect in projects stored on BIM Collaborate / Autodesk Construction Cloud (BIM/ACC). Deleting a report configuration now also updates the list correctly.
Bug fix: PDM 2027: "Unable to load DLL 'e_sqlite3'" when opening a project without Plant 3D installed (PT-5424)
Added missing e\_sqlite3.dll (PDM/PR/PB) for 2027.
Bug fix: Installer copies year/shared DLLs to two LIB locations (\ + \NetCore) - partial update leaves a stale shadow copy in use (PT-5430)
Fixed an installer issue where some PlantTools libraries were copied to two locations; after a partial update this could leave an outdated copy of a library in use.
Bug fix: Cannot import report configurations from a PlantTools.zip (import is disk/.rcf only) (PT-5431)
Report configurations can now be imported directly from another project's PlantTools.zip, in addition to loose .rcf files on disk.
Bug fix: Switching report-files location to Project must write .rcf/layout straight into PlantTools.zip (no loose files) (PT-5433)
When switching the report configuration location to a project, the report (.rcf) and layout files are now written directly into the project's PlantTools.zip instead of being temporarily created as loose files in the project folder.
Bug fix: PrePrint (Versions/Revisions) settings are not zip-aware - empty ACPlantTools\PlantReporter folder created and RevisionSettings.xml does not persist in migrated projects (PT-5436)
Versions/Revisions (PrePrint) dialog settings are now stored in and read from the project's PlantTools archive in migrated projects, so they persist correctly. The dialog no longer creates an unnecessary empty 'ACPlantTools\PlantReporter' folder.
Bug fix: xml files in ACPlantTools folder and the PT sub folder are not removed when migrating a vault project (PT-5443)
If a project already has the PlantTools configuration files migrated, then remaining empty folders under the ACPlantTools folder will be removed.
Bug fix: Error message when trying to import a rcf where the layout is 24.2 (PT-5444)
An error appeared when importing rcfs when PR waas set to 2026.
Bug fix: Dark mode: native WinForms controls (buttons, group boxes, etc.) render in light style across PlantTools UIs (PT-5476)
Fixed numerous dialogs and wizards across PlantTools (PDM, PET, PSD, PL, PR) that displayed light-coloured buttons and control areas when the dark UI theme was active, so these screens now render consistently in dark mode.
Bug fix: PDM/PR standalone install fails license activation: missing System.Management.dll (PT-5491)
Fixed an error where installing PlantDataManager or PlantReporter on its own could fail license activation with a missing System.Management assembly. The required file is now shipped by the standalone installers.
Bug fix: Harden PlantTools assembly resolution: greedy AssemblyResolve in shared Libraries serves wrong-version/non-PT DLLs into AutoCAD -> crashes (net10 System.* leak; Advanced Steel enabler load failure) (PT-5494)
Fixed a crash ("Could not load file or assembly 'System.Runtime, Version=10.0.0.0'") when opening a project or signing in to a collaboration project in AutoCAD Plant 3D 2025 and 2026. The shared program libraries no longer ship .NET 10 versions of the Microsoft.Extensions and System.Management components into the .NET 8 runtime folder.
Bug fix: PlantBatch command-line mode does not download ACC/Vault collaboration projects before running a batch (PT-5495)
PlantBatch can now open ACC and Vault collaboration projects directly from the command line: the project is downloaded automatically before the batch runs. Previously this worked only through the interactive project-open dialog, and command-line runs silently used a local project instead.
Bug fix: PT bundles Autodesk PnP*/ac* runtime DLLs that shadow the installed P3D build -> 'Method not found: DocumentServer.get_DisplayRegion()' crash on project open (PT-5497)
Fixed a crash ("Method not found: DocumentServer.get\_DisplayRegion()") when opening a project or the collaboration project list in AutoCAD Plant 3D after the AutoCAD Plant 3D installation had been updated. PlantTools no longer ships copies of Autodesk's own Plant 3D runtime libraries that could override the installed ones.
Bug fix: Report configuration import fails with 'Version string portion was too short or too long' when the folder contains layout backup files (PT-5498)
Importing a report configuration could fail with the error 'Version string portion was too short or too long' if the source folder contained backup or renamed copies of layout files (for example names ending in .bak or with a date such as \_241219). These extra files are now ignored during the import, so the import completes normally.
Bug fix: GenericDialog buttons and "Show details" appear in the Windows display language instead of the selected PlantTools language (PT-5510)
Dialog buttons and the "Show details" link now always appear in the language selected in PlantTools instead of the Windows display language.
Bug fix: Editing an existing report in a Collaboration project is not checked in and does not increment the Forma version (PT-5514)
Editing a report in a Collaboration project now checks the change in and increments the version in Forma.
#### Version 10.0.0.5101 (18.06.2026)
New: Update to Plant 3D 2027 and DevExpress 25.2.6 (PT-5148)
PlantTools now support AutoCAD Plant 3D 2027.
PlantTools support AutoCAD Plant 3D 2022 - 2027 now.
Updated DevExpress controls and tools to version 25.2.6 in all PlantTools.
New: Implementing F1 and ? button in title all UIs (PT-4523)
Added F1 support to all dialogs including a ? button in the title bar.
New: All PlantTools configuration files in one zip file (PT-4867)
All PlantTools configuration files are stored in the PlantTools.zip file.
See: [One zip file](https://documentation.auxalia.com/EN/PlantTools.html?pt_support_onezipfile.htm)
New: Added a Kill executable option (PT-5252)
When using Vault or Collaboration projects the script file cannot always be finishing its last lines after the last drawing get closed. In this case there is only the kill option. The delay can be set as well.
New: Auto-dismiss Undo Checkout Dialog option (PT-5253)
When using Vault or Collaboration projects using PLANTUNDOCHECKOUT or PLANTVAULTUNDOCHECKOUT let the UNDO checkout dialog appear which disrupts the batch process. If the option is enabled, the dialog will be closed automatically after it appeared.
New: Inspect script before execution (PT-5254)
In the settings for a batch configuration you can enable the checkbox which then will show a dialog before the AutoCAD script gets executed. This allows inspecting or making changes to the script file before its execution. This is especially helpful to modify the script when testing.
New: Show dialog when using an invalid report configuration name in the command line (PT-5276)
A dialog appears which shows the report configuration name used in the command line in case the name cannot be found. FOr example when using PlantBatch.
New: Various Improvements for PlantBatch (PT-5310)
* Various improvements and changes around Vault and Collaboration projects.
* Drawings will be checked out by PlantBatch
* Undo Checkout will be applied to checked out drawings
* Completion dialog can be suppressed
* Live progress counter to see the progress
* Extended auto-dismiss function to close additional unwanted Plant 3D dialogs
Changed: Use UserLookAndFeel.Default for skin-style application across forms (PT-5281)
Align all user interfaces to use the same skin.
Changed: Migrated MigrationTool to DevExpress controls (PT-5282)
Changed the user interface and controls of the MigrationTool to DevExpress to have the same look and feel as other UIs.
Changed: Cleanup of orphaned resources and rename to AqaPlantToolResources.10.0.dll (PT-5288)
Removal of all orphaned resource texts and images.
Bug fix: PlantTools updates not installed after closing the application (UpdateInstaller.exe crashed on startup) (PT-5405)
Fixed an issue that prevented downloaded PlantTools updates from being installed after the application was closed.
Bug fix: Delete temporary AutoCAD profile before executing acad.exe (PT-5255)
PlantBatch created a temporary AutoCAD profile to download the selected drawings. After that the profile was not deleted again which let to a wrong profile when starting acad.exe.
Bug fix: PlantBatch didn't use the language setting of like all other PlantTools (PT-5256)
PlantBatch didn't use the language setting of like all other PlantTools.
Bug fix: ACProject.db not registered in project MISC (PDM / PR / PET, normal + collaboration) (PT-5345)
The revisions database (ACProject.db) is now automatically added to the project and, for collaboration projects, synced to the cloud. This applies to Plant Data Manager, Plant Reporter, and Plant Express Tools, for both normal and collaboration projects.
Bug fix: Selecting a Vault project fails with “Access to PlantTools.zip is denied” (Vault mis-detected as non-collaboration) (PT-5397)
Fixed an error that prevented PlantReporter from opening Vault projects. Selecting a Vault project no longer fails with an “Access to PlantTools.zip is denied” message; PlantReporter settings are now correctly checked out of Vault.
Bug fix: No report generated in headless/batch mode (PlantBatch) on collaboration projects — report runs before the project finishes loading (PT-5401)
Fixed PlantReporter not producing a report when run in headless/batch mode (e.g. via PlantBatch) on Vault/collaboration projects. PlantReporter now waits for the project to finish loading before the report is generated.
#### Version 9.2.0.4959 (21.04.2026)
New: Adapting PlantBatch and PlantReporter for Vault (PT-3577)
PlantBatch and PlantReporter work with Autodesk Vault Plant 3D projects as well.
Other PlantTools will follow soon.
New: Move Versions/Revisions/Compare Settings into PlantProjectSetup (PT-4656)
The version/revision setting of PlantReporter and PlantExpressTools' PlantProjectManager were moved to PlantProjectSetup.
The settings from PlantReporter and Categorie Settings will be migrated.
In the Categories Settings of PlantProjectManager you now only see the selected **Configuration Name** pointing to PlantProjectSetup.
In PlantReporter you will find the selected **Configuration Name** also in the Settings as before.
As you can see, the setup is shown in an extended tooltip.
New: New PlantBatch app to batch process (PT-5034)
PlantBatch is a new utitlity added to PlantReporter and PlantExpressTools. It allows executing scripts with Plant 3D or run multiple reports as a batch process.
Details under [PlantBatch](https://documentation.auxalia.com/EN/PlantTools.html?plantbatch.htm)
New: Creating temporary AutoCAD profiles to avoid issues with corrupt profiles (PT-5084)
PlantDataManager, PlantReporter, and PlantBatch create a temporary AutoCAD profile (starting with CLI\_) when using accoreconsole.exe with ACC or Vault projects.
The reason was, that accoreconsole.exe got stuck if the current AutoCAD profile was corrupt. We create a clean new profile which will be removed as soon as the accoreconsole.exe got started.
Changed: Starting PlantReporter with command line argument /HIDDEN still showed user interfaces during execution (PT-5141)
When using PlantReporter with command line parameters the /HIDDEN parameter still allowed the appearance of the **Loading Project...** and **Progress Panel**.
Now everything is hidden.
Changed: Adapt the build-in Help Browser to support modern URLs (PT-5174)
The build-in help browser used by PlantTools does support modern URL now. This is in preparation of switching the documentation to GitBook.
Bug fix: Adapt GenericDialog and ProgressBar to show the PlantTools name which is opening the dialog (PT-5010)
Out Generic Dialog and Progress Bars often shows the wrong PlantTools name.
Bug fix: Newly created projects uploaded to ACC cannot be opened in PlantReporter / PlantDataManager due to Project.xml version error (PT-5081)
When opening a newly created 2025/2026 ACC project with PlantDataManager/PlantReporter an error appeared.
The reason was a new ProjectVersionMinor with 2025/2026 in Project.xml.
Bug fix: Script error in Layout Designer (PT-5177)
Script error when opening a report design after using Preview.
Bug fix: Missing Microsoft.Data.SqlClient.dll (PT-5220)
AutoCAD Plant 3D is using the Microsoft.Data.SqlClient.dll since 2026. Before that it was System.Data.SqlClient.dll. THis has been fixed.
#### Version 9.1.0.4754 (19.12.2025)
New: Allow disabling/enabling scripting in PlantReporter layouts CX (PT-4276)
With PR 8.0.0 we enabled scripting as it was before. However, DevExpress disabled it by default for security concerns.
Bug fix: Highlighting and Prefixes for changes in Version/Revision Comparisons for excel exports not working under specific settings (PT-4416)
The color highlighting and prefixes for Excel exports are not working under certain settings.
Bug fix: Report creation dialog must be completed twice (PT-4664)
When creating a new report configuration, the New Report Configuration dialog had to be filled out twice. empty.
Bug fix: Exception when creating a new report and opening the query (PT-4677)
When creating a new report configuration an error occured when clicking on the Edit Query button.
Bug fix: Empty report generated when using “Compare Versions/Revisions” in PlantReporter (PT-4921)
Due to data type mismatch between Plant 3D databases and the ACProject database for Boolean data the report was empty.
Bug fix: Error when files exist which do not end rcf or a layout version when opening a project (PT-4925)
If files other then \*.rcf or \*.layout.xx.x exist in the folder for the report templates an error appeared.
Bug fix: Error when opening project in PlantDataManager/PlantReporter with ACAD 2026 setting and no Plant 3D installed (PT-4929)
Due to missing dlls for Plant 3D 2026, PlantDataManager and PlantReporter couldn't load a project when trying to load the PlantTools config files.
Bug fix: Incorrect coloring and change detection in compare reports when objects are added between versions (PT-4999)
When comparing two version of a report, all rows were shown as added. This was due to the fact, that the name of the project stored in the ACProject.db was also considered for the comparison. But when the project was renamed between versions, they all appears as new. Now the project name is not considered anymore, because the ACProject.db exists for each project separately.
Bug fix: The column Filter in Query dialog is read-only (PT-5003)
The column Filter couldn't be edited anymore.
For filtering we recommend using filtering within the layout which is much more powerful.
Bug fix: Licensing error when opening project in PR with not P3D 2026 installed (PT-5008)
Due to a mix-up in the files for the creation of the PlantReporter\_Setup.exe PlantReporter could be started if no Plant 3D 2026 was installed.
Bug fix: Missing Microsoft Redistributable dependency check when installing PlantDataManager or PlantReporter (PT-5009)
When PlantDataManager or PlantReporter are installed or updated we now check if the Microsoft Visual C++ 2015-2022 Redistributable (x64) is installed. If Plant 3D is installed, then this package already exists, but without Plant 3D this package may be missing, but it is required by PlantDataManager and PlantReporter.
#### Version 9.0.1.4615 (07.08.2025)
Bug fix: Closing PlantProjectSetup of PlantExpressTools Ribbon creates a FATAL ERROR (PT-4914)
When closing the PlantProjectSetup dialog the PlantToolsSetup.xml got checked in, but then Plant 3D crashed with a FATAL ERROR.
#### Version 9.0.0.4602 (05.08.2025)
New: Update to Plant 3D 2026 and DevExpress 24.2.6 (PT-4744)
PlantTools now support AutoCAD Plant 3D 2026.
PlantTools support AutoCAD Plant 3D 2021 - 2026 now.
Updated DevExpress controls and tools to version 24.2.6 in all PlantTools.
Change: Wait dialog in the center of the app and not on top of the screen (PT-4758)
The Wait dialog was always at the top of the screen. Which was very annoying if you wanted to use other apps while waiting. Now the Wait dialog is only on top of the PlantTools or Plant 3D. Also, it is now centered on the app (e.g., PlantReporter) which is opening the Wait dialog.
Change: Convert InfoBox into DevX controls (PT-4874)
The Info Box Dialog got migrated to DevExpress controls to get the same look and feel as the other UIs.
Bug fix: The PlantCloudCLI_Log.txt file is not created anymore (PT-4879)
The C:\ProgramData\ACPlant Consult\PlantTools\Log\*\*PlantCloudCLI\_Log.txt\*\* log file wasn't created anymore. The log file is used when PlantDataManager or PlantReporter calls the accoreconsole.exe to execute the Collaboration functions.
#### Version 8.3.0.4426 (07.05.2025)
New: Update to maintain compatibility with other PlantTools (Details)
This update is required to maintain compatibility with other PlantTools, despite no new features, changes, or bug fixes being included.
#### Version 8.2.0.4346 (28.02.2025)
New: Adapted Version/Revision/Compare function for Collaboration Projects (PT-4434)
As a first step we make the version/revision/compare function available for Collaboration Project using the same workflow as before and store the data in the \ACPlantTools\ACProject.db.
New: Including the Date/Time and User Name in the selection list when selecting the Version/Revision when comparing (PT-4388)
The selection lists for Previous and Newer Version/Revision show:
* Version or Revision
* VersionNumber
* DateTime
* UserName
The list is also ordered by the DateTime value. Oldest at the bottom.
New: Adapt PlantReporter UIs to DevExpress (PT-4556)
All PlantReporter user interfaces were updated to DevExpress controls.
Bug fix: Texts for Proxy Settings aren't changed right away when switching the language setting (PT-4103)
When switching the language, the labels for the proxy settings are not updated, but all other labels.
Bug fix: Error Opening Collaboration Project on First Download via PlantDataManager/PlantReporter with 2025 (PT-4546)
When attempting to open a Collaboration Project via PDM or PR that has not yet been locally downloaded, an error is displayed stating that the project file cannot be found. This issue is specific to setups using the 2025 and does not occur with earlier versions.
Bug fix: Versioning/Revisioning UI always opens in the top left hand corner of the screen in PlantReporter (PT-4553)
The user interface to create versions/revisions always opens in the top left hand corner of the screen.
Bug fix: Previous Version/Revision value is always 0/A (PT-4554)
The value of the Previous Version is empty at the beginning (which is correct), but when it is 0 after that, it will stay 0 forever and not show the correct previous version.
Bug fix: If a settings .bak file exists and is NOT writable an error appeared (PT-4868)
When settings files were supposed to be overwritten, but an existing bak files was set as read-only, then an error appeared when PlantTools tried to create a new bak file.
This typically happened with Collaboration Projects.
#### Version 8.1.0.4182 (15.11.2024)
New: Query now shows the Class and Property Display Names (PT-4195)
When starting PlantReporter with [Command line](/plant-tools/plantreporter/how-to-use/command-line.md) parameter the parameters weren't passed through from the PlantReporter.exe to the PlantReporter.FrameWork.exe or PlantReporter.NetCore.exe.
New: Redesign of Version/Revision dialog (PT-4387)
The button **Create without versioning** be be changed as another option.
New: Order Versions/Revisions chronologically in Selection Lists when comparing (PT-4394)
The comboboxes when selecting the previous and newer version/revision show the versions and revisions in chronological order from newest at the top and oldest at the bottom.
New: Adding type of version/revision as variables for the report file name (PT-2597)
We added two new variables **REVTYPE1** and **REVTYPE2** which holds V or R.
The variables can then be used in the Export file path.
Bug fix: Command line parameters aren't passed through from PlantReporter.exe to PlantReporter.FrameWork.exe/PlantReporter.NetCore.exe (PT-4335)
When starting PlantReporter with [Command line](/plant-tools/plantreporter/how-to-use/command-line.md) parameter the parameters weren't passed through from the PlantReporter.exe to the PlantReporter.FrameWork.exe or PlantReporter.NetCore.exe.
Bug fix: Report Layout files of version 22.2 aren't downloaded (PT-4341)
When opening a Collaboration project the PlantReporter layout files of version 22.2 weren't downloaded. Only the rcf files.
Bug fix: Error when ordering Plant 3D projects in Open Collaboration Project dialog (PT-4271)
When opening a Collaboration Project in PlantReporter or PlantDataManager an error appeared.
#### Version 8.0.0.4046 (28.08.2024)
New: Update to Plant 3D 2025 and DevExpress 23.2.6 (PT-3326)
PlantTools now support AutoCAD Plant 3D 2025.
PlantTools support AutoCAD Plant 3D 2020 - 2025 now.
Updated DevExpress controls and tools to version 23.2.6 in all PlantTools.
New: Show AutoCAD Version in title of PlantDataManager/PlantReporter (PT-4154)
The title of PlantDataManager and PlantReporter shows the set AutoCAD version now.
Change: Adapt Plant Report Layout Version Check (PT-4132)
Due to the upgrade to DevExpress 23.2.6 the layout files must be updated as well.
If you have PlantReporter set to 2025, you first need to change the setting to 2024 again in order for PlantReporter to be able to migrate the layouts. Otherwise you will see this dialog:
During the migration of the layout you will be shown a progress bar.
After the layout have been migrated you can switch back to 2025.
Bug fix: Preview and Print/Export buttons will not be activated anymore, if a report but no project was selected (PT-4118)
To avoid an error message the Preview and Print/Export buttons will be deactivated now in case no project has been selected, but a report configuration.
#### Version 7.2.0.3767 (26.04.2024)
New: Implementing a File Watcher to monitor the CLI file content for support cases (PT-3455)
A file watcher is implemented to check which communication between PlantDataManager/PlantReporter and the acccoreconsole.exe is exchanged. This is especially useful when helping customers with support.
Details can be found under [File Watcher](/plant-tools/planttools-support/file-watcher.md).
New: Add PlantTools configuration files to the MISC database for Non-Collaboration projects (PT-3376)
When using Collaboration projects PlantDataManager and PlantReporter adds configuration files (e.g. for links, calculation, reports and so on) to the MISC database to have them shown under the Related Files folder in Project Manager. This is also important when using **Create Project Backup** with Project Manager, that these PlantTools configuration files are also backed up.
The following files are handled:
* Report Configuration Files (rcf) & Layout Files (\*.layout.xx.x) & ReportConfiguration.Collection.xml
* Link Configuration Files (lcf) & Related Files (udl, SQLite, accdb, mdb, xlsx, xls) & LinkConfiguration.Collection.xml
* SQL Scripts (sql)
* Calculation Configuration Files (calc) & CalculationConfiguration.Collection.xml
* PropertiesPaletteConfiguration.xml
* PDMDataCache\_\[USERNAME].dcf
* NPO\_\[DWGGUID].xml
New: Copy Report Configuration Files when changing the location in the Settings (PT-3313 \& 3314)
When changing the Report Files Location you can now also have the lcf and layout files be copied to the new location.
In addition, you will see the same 4 button as we have in other PlantTools functions (Calculations (PET/PDM), Link Configurations (PL/PDM), Spec Driven Configurations (PSD), List Function (PET), Selection List Function (PET))
New: Checking for Not-Placed Objects (NPOs) which haven't been imported before printing (PT-3431)
Similar to considering changes in PDMDataCache which haven't been imported yet, we also check of NPOs or Relationsships which haven't been imported yet. In the settings we adapted the text to indicate the change of both file types.
New: Adapt PlantReporter to use split data cache files when checking for unimported changes (PT-3540)
Because PlantDataManager is now using PDMDataCahce files per user, PlantReporter needed to be adapted as well in order to check for changes which haven't been imported yet when Printing/Exporting reports.
New: Improved performance when handling PlantTools configuration file with PlantReporter/PlantDataManager for Collaboration Projects (PT-3413)
When PlantDataManager/PlantReporter check or need to download the files referenced in the collection files it will be done now in a batch process to reduce the number of calls to the accoredconsole.exe.
New: Disregard unsupported AutoCAD Versions (PT-3467)
When retrieving information from the registry about the installed version we disregard ACAD versions which the installed PT don’t support.
E.g. a customer has 2025 installed, but the installed PTs support only 2019-2024.
Bug fix: Error when using 'Browse For Folder' dialog to select Export Path for reports (PT-3501)
When creating a new report configuration clicking on the .. button to select a path for the location of the output an error appeared.
#### Version 7.1.0.3490 (01.12.2023)
New: Improved text information in Progress Panels when downloading, checking out/in, or removing PlantTool files (PT-2486)
if PlantTools download/check out, check in, or remove one of its configuration files we now show a progress panel with the file name and path to see which file is handled.
New: Speed improvement when opening a Collaboration project in PlantDataManager and PlantReporter (PT-2639)
The number of commands to download the various PlantTools configuration files was reduced to greatly reduce the time when downloading the PlantTools files.
New: Do not Check In/Out/Download PlantTools files when using Vault projects (PT-2749)
With PlantTools version 6.0.0.2267 (first support for Plant 3D 2023) we linked the PlantTools files (located under \[PROJECT]\ACPlantTools) into the MISC.dcf database so the PlantTools files appear under the **Related Files** folder in Project Manager. However, this cause a problem with Vault projects when we started to check in/out/download the PlantTools files for Collaboration projects in later versions.
Now the PlantTools files are still linked into the MISC.dcf, but they are not checked in/out/downloaded anymore if current project is using Vault.
You can now just copy PlantTools files from another project or template project into your Vault project and open the project in Plant 3D again. Alternatively, you can follow the [Workflow with Vault and PlantTools](https://documentation.auxalia.com/EN/PlantTools.html?whitepaper_pt_files_on_vault.htm).
Bug fix: PlantDataManager/PlantReporter cannot get accorconsole.exe instance in time (PT-2598)
When PlantDataManager/PlantReporter use Collaboration projects the accoreconsole.exe will be started in the background to execute the BIM functions (refresh, check out/in, , download). Sometimes the start of accoreconsole.exe took to long. Now they retry till the accoreconsole.exe is ready.
Bug fix: Error when comparing versions/revisions with different values if the property is used in the filter expression (PT-1971)
Comparing versions/revisions of reports where an expression is used in the layout results in an error message.
Bug fix: Comparing reports for 3D parts doesn't show correct coloring and the quantities are missing (PT-1054)
When creating a comparison report only new parts are shown in green, but the deleted parts don't show with red background at all.
Quantity changes are not shown in yellow. In addition, no quantities are shown at all.
Bug fix: Error when using 'Browse For Folder' dialog to select Export Path for reports (PT-2600)
When using the **Browse** button to select a folder where the reports are supposed to be created and clicking OK...
...this error appeared.
Bug fix: Error message when selecting some older rcf file (PT-2609)
Sometime selecting an older RCF file resulted in an error. The error appeared, because PlantReporter wasn't able to change the RCF file into the new RCF+Layout file format.
#### Version 7.0.2.3307 (04.08.2023)
Bug fix: Update needed because of old digital certificate was used (Details)
We forgot to update the new digital certificate in the Setup.exe and Update.exe. This is necessary to let Windows and AutoCAD know, that our files are trustworthy.
#### Version 7.0.1.3289 (03.08.2023)
Change: Because of compatibility reasons, PlantReporter must be updated as well (Details)
PlantTools use common code which sometimes make it necessary to update all PlantTools at once even if there are no changes to a specific PlantTool.
Version 7.0.0.3143 (07.06.2023)- New: Adapted PlantTools for AutoCAD Plant 3D 2024 (PT-2112)
PlantTools now support AutoCAD Plant 3D 2024.
PlantTools support AutoCAD Plant 3D 2019 - 2024 now.
New: Automatically reload project if PlantReporter wants to restart after choosing a different AutoCAD version (PT-2282)
If PlantReporter restarts because of a change of the AutoCAD version setting, a previously loaded project will be reloaded.
New: Added execution of SQL Scripts when loading a project (PT-2059)
Allow the execution of SQL Scripts when a project is loaded. This helps with the creation of views often used for PlantLink. And avoids the manual execution of SQL Scripts when a project has just been created.
It is also important when using Collaboration projects, because the views used by PlantLink do not exit when the project is first downloaded to the local work folder.
Details under: [Execute SQL Scripts on Project Load](/plant-tools/plantlink/how-to-use/usage/execute-sql-scripts-on-project-load.md)
New: Separation of Report Layout from 'Report Configuration File (RCF)' (PT-2299)
Due to the fact, that the report layout of DevExpress 22.2.5 isn't backwards compatible with DevExpress 21.2.6 we start to split up the report layout information (stored in the RCF files) in a separate file with the DevExpress version number. This way we don't run into the incompatible issue again in the future, because we can fall back on the previous DevExpress version for the layout.
Since Report Configuration files can be used in PlantDataManager too, PlantDataManager will also trigger the separation of the rcf file into 2 files.
The new file with the layout info is stored in the \[RCFNAME].layout.22.2 file where 22.2 is the current DevExpress version used with the 7.0.0.x PlantTools.
New: Filtering Spec Sheets from drawing reports (PT-2377)
When using the **Drawings** query option, the Spec Sheets of Plant 3D (stored in the PnPDrawings table in the Piping.dcf database) where also included in the list. Now they are filtered out.
Change: Updated to DevExpress 22.2.5 for all PlantTools (PT-2121)
We updated DevExpress controls and tools to the latest version 22.2.5 in all PlantTools.
Change: Deleting Report Configuration Files will move the the files to the Windows Recycle Bin (PT-2323)
Up until now the RCF file was just deleted when the user deleted a report configuration.
Now all files related to the deleted report configuration are moved to the windows Recycle Bin.
Change: Log file isn't written in the correct path (PT-2141)
The Log files are written into the %programdata%\ACPlant Consult\PlantTools\Log folder.
Existing log files will be moved from the old folder to the new folder.
For convenience there is a folder junction in the old location %appdata%\ACPlant Consult\PlantTools\Log
Change: Remove Groups tab from PlantReporter Settings (PT-2331)
We removed the grouping function to group Plant 3D projects or other data sources. Therefore the tab in the Settings isn't needed anymore.
Change: Remove Other Data Sources tab from PlantReporter Settings (PT-2332)
We removed the ability to use other data sources in PlantReporter. Therefore the tab in the Settings isn't needed anymore.
Change: Remove Other Data Sources tab from the main form of PlantReporter (PT-2333)
We removed the ability to use other data sources in PlantReporter. Therefore the tab in the main dialog isn't needed anymore.
Change: Remove Groups selection from the Project dropdown control (PT-2334)
We removed the grouping function to group Plant 3D projects or other data sources. Therefore the group selection in the project dropdown list isn't needed anymore.
Bug fix: Opening projects < version 2018 ends in endless loop of restarts (PT-1754)
When opening a project with Plant 3D version 2018 or older, PlantReporter set the appropriate version (e.g. 2017 and restarts). After it then automatically opens the project again you get the same message again. This is an endless cycle.
Now the user gets the info to first migrate the project.
Bug fix: PlantReporter resets settings to default values (PT-2271)
When closing PlantReporter the PlantReporter.xml with the settings was written with default values, but the file wasn't supposed to be written when PlantReporter gets closed. Only when closing the PlantReporter Settings dialog.
Bug fix: PlantReporter doesn't restart when changing the AutoCAD version if a project is already loaded (PT-2270)
When changing the AutoCAD version in PlantReporter Settings with a project already being loaded, PlantReporter didn't start after clicking Yes on dialog #00765.
Bug fix: PlantReporter writes errors in Log file if a Non-BIM project is loaded (PT-2287)
When opening a regular network project (not a Collaboration project), then the Log file showed error messages.
Bug fix: When downloading a BIM project using a UDL file for a Link Configuration, the referenced file in the UDL file isn't downloaded in PlantReporter (PT-2222)
PlantReporter and PlantDataManager downloaded the UDL file, but the referenced file in the UDL file (e.g. an MS Access DB) wasn't downloaded. Only when you opened the project again was the referenced file downloaded.
Version 6.4.0.3019 (07.04.2023)- New: PlantReporter adapted to handle PlantLink files for Collaboration Projects (PT-2056)
Due to the adaptation of PlantLink for Collaboration Projects, PlantReporter is also handling link configuration files for Collaboration Project.
Details regarding the various workflows when using Collaboration Projects can be found under [Collaboration Workflows](/plant-tools/plantreporter/collaboration-workflows.md).
New: Common PlantTools settings (Language, DevExpress Skin, Update Check, Proxy Setings) are moved to PlantProjectSetup (PT-289)
As part of the strategy to move all PlantTools settings into PlantProjectSetup, we started moving the common settings Language, DevExpress Skin, Update Check, and Proxy Settings into PlantProjectSetup and make it accessible through all Desktop PlantTools (PC, PDM, PR) and Plugins (PCD, PDM Plugin, PET, PL, PS, PSD).
Details can be found under: [PlantProjectSetup](/plant-tools/planttools/plantprojectsetup.md)
New: New Update Installer (PT-867)
As part of the move of the common PlantTools settings (Language, DevExpress Skin, Proxy Settings) we also updated the Update Installer.
Details can be found under: [Update Installer](/plant-tools/planttools/update-installer.md)
New: Use the last Collaboration Account and Project when using 'Open Collaboration Project...' in PlantDataManager/PlantReporter (PT-2095)
When using the dialog to open a Collaboration project, the previously used Collaboration Account and Project will be preset. This behaviour is consistent with AutoCAD Plant 3D.
Change: Use Retry function when trying to load Collaboration Accounts, Projects and Plant 3D projects (PT-2102)
The Plant 3D Collaboration API used in PlantDataManager and PlantReporter isn't very reliable. Therefore PlantDataManager/PlantReporter sometime get empty values. This happens for example when PlantDataManager/PlantReporter try to get the available Projects for the user interface. Now we try multiple-times with a delay in between to make sure we get data.
Bug fix: Adapt PlantReporter to include the ACC location (US or EU server) (PT-2079)
The server location of Collaboration projects wasn't considered yet.
Bug fix: PlantDataManager/PlantReporter crash when using 'Open Project' in the 'Collaboration for Plant 3D' dialog, but no Plant 3D project was available (PT-2100)
When you opened the Collaboration for Plant 3D dialog, but no Plant 3D project was available, PlantDataManager and PlantReporter crashed when you clicked on Open Project.
Bug fix: PlantTools don't work with French Plant 3D because the AutoCAD language code wasn't supported (PT-2156)
The AutoCAD language code for French Plant 3D wasn't supported in PlantTools. This effected all PlantTools.
Bug fix: Collaboration Project was downloaded a second time if it was already downloaded with PlantDataManager/PlantReporter (PT-2103)
When a Collaboration project was downloaded with PlantDataManager or PlantReporter first, and the the project was opened with Plant 3D, the project was downloaded again as a copy.
Version 6.3.0.2824 (03.02.2023)- New: This release is necessary to stay compatible with other PlantTools due to shared files. This release doesn't contain any Bug fixes, Changes, or New functionality (Details)
PlantTools are using shared/common files which for some releases makes it necessary to release PlantTools, although there is no bug fixing, change or new functions had been implemented.
This is especially important when PlantTools are installed or updated in the wrong order.
Version 6.2.0.2759 (21.11.2022)- New: Support for opening collaboration projects in PlantReporter which don't exist in the local work folder yet (PT-1872)
PlantDataManager and PlantReporter can now open Collaboration projects which haven't been opened with Plant 3D before and therefore aren't available in the local work folder yet.
Before using PlantDataManager or PlantReporter make sure that you have read [Using ACC/BIM projects with PlantDataManager](/plant-tools/plantdatamanager/how-to-use/using-collaboration-projects.md) and [Using ACC/BIM projects with PlantReporter](/plant-tools/plantreporter/how-to-use/using-collaboration-projects.md)!
Change: Improved loading time when opening a project (PT-1826)
Improved the speed when pre-synching ACP tables when loading the project.
Bug fix: Check if AutoCAD Plant 3D 2023 is installed when trying to open collaboration projects (PT-1864)
PlantDataManager didn't check if Plant 3D 2023 was installed which caused error when trying to open collaboration projects.
Bug fix: Fixed path to DevX dlls in PlantToolsCommon project (PT-1917)
Some files had a wrong path to the Development Express DLLs in the PlantToolsCommon project, which potentially could could error for some controls. However, that apparently never became an issue.
Bug fix: PlantReporter disables the Version/Revision feature (PT-1861)
In some cases the Version/Revision tab and function was deactivated depending on the 'AutoCAD Version' setting, but the availability is only depending on the project type. For Vault and ACC projects the feature is currently not available.
Version 6.1.0.2575 (26.08.2022)- New: PlantDataManager and PlantReporter adapted for Collaboration Projects (BIM360/ACC) (PT-1623)
PlantDataManager and PlantReporter do support Collaboration projects. This is only available for AutoCAD Plant 3D 2023 and future versions, because if new technology Autodesk implemented in AutoCAD Plant 3D 2023, but not lower versions.
Before using PlantDataManager or PlantReporter make sure that you have read [Using ACC/BIM projects with PlantDataManager](/plant-tools/plantdatamanager/how-to-use/using-collaboration-projects.md) and [Using ACC/BIM projects with PlantReporter](/plant-tools/plantreporter/how-to-use/using-collaboration-projects.md)!
New: New Update Installer (PT-1714)
To avoid issues with different build versions of PlantTools, we now force users to update all installed PlantTools to avoid any issues with shared files between PlantTools.
After installing one PlantTool and not updating others you will see the following dialog which allows you to individually download PlantTools or to download all available updates at once (green arrow).
The updates will be downloaded and stored in the download folder.
After closing the desktop PlantTools (PlantCenter, PlantDataManager, PlantReporter) or closing Plant 3D the downloaded updates will be installed automatically.
Change: Disable the UI when loading/refreshing project to prevent unexpected results in case the user interacts while loading is being processed (PT-1758)
When opening a project in PlantDataManager or PlantReporter the user interface is disabled so the user cannot interact with the user interface while the project is being loaded. Interacting with the user interface caused issued with when loading collaboration projects.
Bug fix: Duplicate project folder names in MRU (most recently used) list causes an error (PT-1752)
In cases were a project name appeared multiple times, there could be an issue when opening a project, because the correct path to the selected project couldn't be identified.
Bug fix: Error (Dialog #00487) when opening a project with no MISC database (PT-1675)
When opening a project where the MISC database doesn't exist you get an error.
This applies typically to old projects where the MISC database didn't exists from project creation on. Only when you added files or folders under 'Related Files' was the MISC database created.
The Plugins like PlantClashDetection, PlantDataManager, PlantExpressTools, PlantLink, PlantSpecDriven and PlantSync will create the file on project load.
PlantDataManager and PlantReporter show the following dialog as an info. The project will be loaded anyway.
If you extend the dialog you get information on how to create the MISC database.
#### Version 6.0.0.2267 (19.04.2022)
New: Adapted PlantTools for AutoCAD Plant 3D 2023 (PT-1571)
PlantTools now support AutoCAD Plant 3D 2023.
PlantTools support AutoCAD Plant 3D 2018 - 2023 now.
Change: Updated to DevExpress 21.2.6 for all PlantTools (PT-1580)
We updated DevExpress controls and tools to the latest version 21.2.6 in all PlantTools.
Change: Remove ACPAssetOwnership table (PT-1554)
The ACPAssetOwnership table in the ProcessPower.dcf (P\&ID Database) isn't needed anymore and therefore will be removed. The relationships stored in that table between **Placed Objects** and **Not-Placed Objects** used in PlantSpecDriven as already stored
Bug fix: Having an apostrophe in the User Name or PC Name causes problems when accessing PlantTools databases (PT-737)
If the Windows user name contains an apostrophe it cause error when PlantTools tried to access one of its databases (PDMDataCache.dcf, ACProject.db, ACPChangeLog.dcf, ACPProcessPower.dcf)
#### Version 5.0.2.2163 (10.03.2022)
Bug fix: Migration fails because of duplicate PnPIDs in ACPProcessPower and ProcessPower databases (PT-1544)
Because of duplicate PnPIDs in ACPProcessPower and ProcessPower databases the migration failed.
Bug fix: PlantReporter installation is missing the DarkSkin2020.dll (PT-1542)
The installation if PlantReporter was missing the DarkSkin2020.dll. Because of that, PlantReporter didn't even start.
#### Version 5.0.1.2128 (25.02.2022)
Bug fix: Wrong PnPID converted while migrating ACPProcessPower to ProcessPower (PT-1525)
While migrating ACPProcessPower into ProcessPower it could happen that both databases contain the same PnPID. If this PnPID is used inside relationships it happened that the wrong PnPId (the one from ProcessPower and not the one from ACPProcessPower) got converted.
This resulted in a silent exception and therefore wasn't obvious to the user.
Bug fix: Obsolete relationships in ACPProcessPower where the owner doesn't exist anymore (PT-1527)
The ACPRelationships table can contain owner PnPIDs where the PnPID doesn’t exist (anymore). Those relationships will be ignored, but written into the log file if you see the following dialog:
Bug fix: Migration of Not-Placed Objects (NPOs) ignores NPOs not related to a DWG (PT-1528)
Not-Place Objects that are not linked to a drawing were ignored while migration of the NPOs from the ACPProcessPower to the ProcessPower database, if this object does not have a relationship.
#### Version 5.0.0.2090 (15.02.2022)
New: Show info dialog if installed PlantTools doesn't have required minimum version (PT-1441)
With version 5.0 all PlantTools will be updated to that version. Because of shared resources and code is mandatory that all PlantTools on a machine are updated. If this is not the case the following dialog will appear and lists all the installed PlantTools on a machine and which ones require an update.
The PlantTools with the red arrow require an update. The dialog will appear until all PlantTools are updated to the required version.
New: Global Language Setting for all PlantTools (PT-1417)
The language of PlantTools can be set globally now. In the Plugins (PlantClashDetection, PlantDataManager Plugin, PlantExpressTools, PlantLink, PlantSpecDriven, PlantSync) you can select AutoCAD, English, or German. AutoCAD tells the PlantTools to use the AutoCAD language. If you change the setting, the PlantTools Plugins will change the language of the user interfaces and ribbons instantly.
If you select English or German in the Plugins, the Desktop Apps (PlantCenter, PlantDataManager, PlantReporter, MigrationTools and PlantProjectCreate will use this language.
If you select a language in one of the Desktop App Settings, all Desktop Apps will use this language and not the AutoCAD language.
New: Using ProcessPower.dcf for Not-Placed Objects (PT-1079)
The ACPProcessPower.dcf database hosted the Not-Placed Objects (NPOs) which were created by PlantSpecDriven or PlantDataManager, and also used by PlantReporter.
The NPOs will now be stored in the ProcessPower.dcf (P\&ID database) directly. This applies to SQL-Server projects as well.
The advantage is, that when using Vault or ACC/BIM projects, those NPOs will also be check in/out.
The first time you open a project PDM, PDM-Plugin, PET, PL, PR, or PSD will migrated an existing ACPProjectPower.dcf and its content into PID's ProcessPower.dcf.
If you are updating any of the following PlantTools (PlantDataManager, PlantExpressTools, PlantLink, PlantReporter, PlantSpecDriven) you MUST make sure, that the other PlantTools you have installed are also updated to version 5.0.0.x.
New: Deactivation of Version/Revision feature in PR for Vault/ACC projects (PT-1399)
When using Vault or ACC (BIM) projects the version/revision feature is deactivated. The reason is, that the ACProject.db cannot be checked in/out.
We may be able to find a solution with Plant 3D 2023.
#### Version 4.0.0.1441 (24.04.2021)
New: Support for AutoCAD® Plant 3D 2022 (PT-1027)
We now support AutoCAD Plant 3D 2022.
The new "Project Compare" is included in PlantProjectManager also.
New: auxaliaLicenseManager automatically runs "Check for Updates..." (PT-160)
PlantTools trigger the "Update License" check of the network license in auxaliaLicenseServer service on your server.
auxaliaLicenseServer is checking the license every 15 min to ensure, that your license information (e.g. number of license, expiration dates) are updated automatically without your need for involvement.
There is no need to keep the auxaliaLicenseManager open.
If a PlantTools is started and it finds an older CADSTUDIOLicenseManager or auxaliaLicenseManager installed on the server, the following dialog shows up.
You can decide when you want to be reminded again. The maximum is 2 weeks. After that, you will have a maximum of another week, then another 4 days and so on. That gives you a grace period of 4 weeks till auxaliaLicenseManager must be updated. If you don't do this, you will be reminded every time the PlantTools is asking for a license.
Change: Updated to DevExpress 20.2.6 (PT-1043)
We updated DevExpress controls and tools to the latest version 20.2.6 in all PlantTools.
Change: No support for AutoCAD P\&ID 2016/2017 and AutoCAD Plant 3D 2016/2017 (PT-1035)
We discontinue the support for AutoCAD P\&ID 2016/2017 and AutoCAD Plant 3D 2016/2017.
Typically we only removed only one version when adding the newest AutoCAD Plant 3D version, but since hardly any customer is using AutoCAD P\&ID 2017 or AutoCAD Plant 3D 2017 anymore we decided to cut off the two oldest versions. Another argument was, that there is no migration needed between 2018 and 2022 which makes it more convenient for customers t use those newer versions.
Change:Changed Trial Period from 30 to 14 days (PT-975)
PlantTools will run run 14 days in trial period before they stop working.
Change: More informative licensing dialogs (Details)
Several dialogs informing about anything related to licensing (expiration dates, rental dates, issues with activation and more) have been improved to make it clearer what the dialog is all about.
Bug fix: Registry access error (Dialog #00084) after installing PC, PDM, PR and unsuccessful activation in PCD, PL, PS, PSD (PT-1295)
When installing PlantCenter, PlantDataManager, PlantReporter on a PC a a dialog informed the user about denied access when starting the PlantTools from the Desktop. PlantClashDetection, PlantLink, PlantSync, PlantSpecDriven had to be activated everytime Plant 3D was started, because the registration information couldn't be written either. This happened only when installing the PlantTool for the first time or after uninstalling previous installations. desktop shortcut.
#### Version 3.2.0.1253 (10.02.2021)
Change: Changing TimeStamp Format and ProjectType Content in ACPChangeLog.dcf-->ChangeLog table and PDMDataCache.dcf-->DataCache table (PT-729)
PlantDataManager will now also use GMT time zone and UTC format (e.g. 2020-07-16T15:16:26Z) when writing changes into the data cache table. Since the data cache table is also used in PlantReporter to check if there are pending changes in the data cache PlantReporter must also be updated.
Change: Implemented F1 to open our own browser (Details)
When using F1 in PlantCenter, PlantDataManager, PlantReporter, MigrationTool, PlantCenter or any button in the PlantTools or PlantExpressTools ribbon we open our own browser window.
Change: Replacing standard Windows Message boxes with our own dialogs (PT-746)
We started to put more information in our Message Boxes to give you more background details to reduce support questions or the need to look into the online documentation.
Also, all dialog boxes have a number which helps with support.
#### Version 3.1.0.794 (06.08.2020)
Change: Changing TimeStamp Format and ProjectType Content in ACProject.db-->ReportRevision table (PT-699)
We changed the timestamp stored in the ACProject.db to GMT timezone and UTC format.
The ProjectType now shows PnID instead of Pid and Piping instead of P3d.
In the ACProject.db we store the version and revisions of reports as well as drawings.
Change: The BIM icons is shown when opening a project from the local BIM work folder (PT-710)
When selecting local BIM project (currently BIM projects cannot be opened directly from BIM 360), we show the BIM icon infront of the project name to indicate that it is a BIM project.
Change: Updated auxalia logo in report files (PT-703)
Replaced the old CADSTUDIO logos with the new auxalia logos for all report configurations we deliver with the installation of PlantReporter.
#### Version 3.0.1.675 (15.06.2020)
Bug fix: Missing 2021 query files for C:\ProgramData\ACPlant Consult\PlantTools\PlantReporter (PT-624)
We forgot to include the 2021 query files in the installer.
Bug fix: Folders and drawings didn't show in alphabetical order (PT-601)
The order of folders and drawings in DWG trees in PlantCenter, PlantDataManager and PlantReporter is now consistent with the order in AutoCAD Plant 3D's Project Manager.
Bug fix: Error when accessing PDMDataCache when using a UNC path (PT-613)
When trying to use Print/Export with a project which uses a UNC Path, the following error message appeared.
This was due to the fact that PlantReporter wants to access the PDMDataCache.dcf to check if there are changes which haven't been imported yet.
#### Version 3.0 (23.04.2020)
* New: Support for AutoCAD® Plant 3D 2021
* Change: Updated to DevExpress 19.2.7
#### Version 2.4 (07.04.2020)
* New: Introducing DevExpress styles to change main UI for example to dark mode
* Change: Internal Cleanup - Reduction of dlls
#### Version 2.3 (30.10.2019)
* Change: Updated to DevExpress 19.1.6
* Bug fix: Missing DevExpress references
#### Version 2.2.1 (28.10.2019)
* Change: New program icons and ribbon images
#### Version 2.2 (19.07.2019)
* New: Check for not yet imported data of PlantDataManager data cache
#### Version 2.1 (18.07.2019)
* New: Support for XLSX and DOCX export formats
* Change: Suppressing prefix and suffix when creating a comparison report when showing only new or only old values
* Change: Replaced radio buttons for dataset comparison with check boxes to allow multiple-choice
* Change: Set "Text Export Mode" for Excel Export to "Text" by default
* Bug fix: The "Fields" option when comparing versions/revisions wasn't implemented correctly
* Bug fix: When comparing revisions, sometimes the following error was shown: "Index was out of range"
* Bug fix: Added dependency: "Visual C++ Redistributable for Visual Studio 2015" when installing the PlantTool
#### Version 2.0 (17.05.2019)
* New: Support for AutoCAD® Plant 3D 2020
* New: Auto-Restart PR when project version doesn't match the version setting in PR
* Change: Updated to DevExpress 19.1.3
#### Version 1.46 (02.05.2019)
* Bug fix: When creating with PlantDataManager, PlantReporter or MigrationTool the PDMDataCache, ACProject or ACPChangeLog databases on SQL-Server the GrantPublicRole wasn't set leading to permission issues
* Bug fix: Error when ReportRevision didn’t exist
* Bug fix: For SQL projects with SQL-Server versions below 2016, some syntax errors were raised when using versions and revisions for reports
#### Version 1.45 (07.06.2018)
* Bug fix: When multiple classes were used in a query and Not-Placed Objects were included, the object type (PO, NPO) was not considered during class data merging
* Bug fix: Comparing reports didn't work anymore since version 1.43.0.0
#### Version 1.44 (16.05.2018)
* Change: MigrationTool - Keep the .bak file
* Bug fix: MigrationTool - Some newer SQL syntax was used and was not compatible with SQL older than 2016
* Bug fix: MigrationTool - Primary keys and columns with autoincrement were not migrated
* Bug fix: MigrationTool - The length of VARCHAR was not migrated
* Bug fix: MigrationTool - For ACPProcessPower I first check if already exists in SQL-Server and delete it first to assure no old tables
#### Version 1.43 (02.05.2018)
* New: Support for AutoCAD® Plant 3D 2019
* New: SQLite databases created by PlantTools will now use the same database type as the project (SQLite or SQL-Server)
* New: A migration tool for PlantTools databases was added to move SQLite databases to SQL-Server
* Change: Updated to DevExpress 17.2.7
#### Version 1.42 (21.11.2017)
* Change: Extended links are supported
* Change: Updated to DevExpress 17.2.3
#### Version 1.41 (19.10.2017)
* Change: Updated to DevExpress 17.1.5
#### Version 1.40 (23.05.2017)
* New: Support for AutoCAD® Plant 3D 2018
#### Version 1.39 (26.04.2017)
* New: PlantReport can migrate Autodesk AutoCAD Plant Report Creator files
#### Version 1.38 (30.03.2017)
* Bug fix: EngineeringItems.Size property for Plant 3D classes wasn’t calculated
#### Version 1.37 (02.09.2016)
* New: Handling of versions/revisions of reports and being able to compare versions/revisions for differences
* New: New report configuration files for versions/revisions
* Change: Updated to DevExpress 16.1.5
#### Version 1.36 (11.06.2016)
* New: Borrowing of network licenses
* Bug fix: Automatically install "Visual C++ Redistributable for Visual Studio 2015" package during setup/update in case is not installed. The package is needed in case no AutoCAD P\&ID/Plant 3D 2017 is installed.
#### Version 1.35 (19.05.2016)
* New: Creating reports from other data sources
* New: Creating groups of AutoCAD® P\&ID/Plant 3D projects or other data sources
#### Version 1.34 (11.04.2016)
* Change: Autodesk changed API between Beta and Final release of AutoCAD® P\&ID/Plant 3D 2017 which caused errors
#### Version 1.33 (07.04.2016)
* New: Support for AutoCAD® P\&ID/Plant 3D 2017 64Bit
* Change: Updated to DevExpress 15.2.7
* Change: The drawings are shown with their DWG file name
#### Version 1.32 (02.07.2015)
* Bug fix: Update needed due to a new PnPDataObjects.dll in SP1 for AutoCAD® P\&ID 2016 and AutoCAD® Plant 3D 2016
#### Version 1.31 (13.05.2015)
* New: Support for AutoCAD® P\&ID/Plant 3D 2016
* Change: Updated to DevExpress 14.2.7
#### Version 1.30 (09.02.2015)
-Change: PipeLineGroups and SignalLineGroups weren't shown when using drawing views (changes in the PnPDataLink table)
#### Version 1.29 (19.01.2015)
* Change: PlantTool is ready for Autodesk Exchange Apps.
#### Version 1.28 (04.07.2014)
* New: Support for AutoCAD® P\&ID/Plant 3D 2015
* Change: The directory for the NPO's database is now: \[Project]\ACPlantTools\ACPProcessPower.dcf.
#### Version 1.27 (06.03.2014)
* New: PlantTools are available as rental versions
* Change: The directory for link configurations is now: \[Project]\ACPlantTools\PlantLink\LinkConfigurations. PlantReporter will first check for link configurations at the new location before checking at the old location \[Project]\LinkConfigurations.
* Change: Updated to DevExpress 13.2.7
#### Version 1.26 (15.08.2013)
* Bug Fix: Issue in Report Designer when editing groups
#### Version 1.25 (19.05.2013)
* New: Support for AutoCAD® P\&ID/Plant 3D 2014
* New: Support of SQL-Server Authentication
* New: Updated to DevExpress 12.1
#### Version 1.24 (27.08.2012)
* New: Support for linking external databases. Only the link type "Extend" will be used. Links of the "Update" type have to be updated through PlantLink within AutoCAD® P\&ID/Plant 3D
#### Version 1.23 (30.05.2012)
* Change: Icons and Logo
#### Version 1.22 (25.05.2012)
* New: Support for Graphical Not Placed Objects (GNPOs) created by PlantDataManager
#### Version 1.21 (29.04.2012)
* New: Support for AutoCAD® P\&ID/Plant 3D 2013
* New: Update to NET 4.0
#### Version 1.20 (15.03.2012)
* New: Support for Not Placed Objects (NPOs) created by PlantDataManager
* Change: Filter examples in the query dialogbox adapted for 2012
* Bug Fix: Drawings are ordered by name
* Change: Updated to DevExpress 11.2
#### Version 1.19 (26.09.2011)
* New: Support for AutoCAD® P\&ID/Plant 3D 2012
* Change: Changing side menus to classic pulldown menus
* Bug Fix: Handvalve relationship xml for 2010 had invalid references
#### Version 1.18 (07.04.2011)
* Bug fix: used trial DevX (report designer) in version 1.17.0.0
#### Version 1.17 (06.04.2011)
* Change: The test phase was changed from 100 attempts to 30 days trial period
* New: The expiration date will be shown in the info box and a message box 14 days prior to the expiration date will be shown.
#### Version 1.16 (01.12.2010)
* Bug Fix: The controls in query definition windows were not displayed correctly in some cases
#### Version 1.15 (29.11.2010)
* New: Switch to online documentation
* New: Update to NET 3.5
* Bug Fix: PnPDrawings fields from reports created with previous versions of PlantReporter were not handled correctly
#### Version 1.14 (08.09.2010)
* New: Using relationships, e.g. a nozzle list delivers the related equipment
#### Version 1.13 (26.05.2010)
* Bug Fix: When creating a report by drawing, PlantReporter always created a project report
#### Version 1.12 (29.04.2010)
* Bug fix: Wrong AutoCAD® 2011 Plant 3D dlls for 64bit
#### Version 1.11 (29.04.2010)
* Bug fix: Error when trying to preview/print some reports
#### Version 1.10 (25.04.2010)
* New: Support for AutoCAD® P\&ID 2011 and AutoCAD® Plant 3D 2011
* Bug fix: Pipe Line Groups didn't deliver any results
#### Version 1.9 (20.04.2010)
* Change: Outbound port for activation requests changed from 19800 to 80
#### Version 1.8 (02.03.2010)
* New: Support for AutoCAD® Plant 3D. Report can be created from the 3D classes.
* New: Proxy server support
* New: Updated to DevExpress 9.3
#### Version 1.7 (01.02.2010)
* New: Enhancements of download process
#### Version 1.6 (09.11.2009)
* New: Updated to DevExpress 9.2
* New: Remember most recently used projects
* New: Now shows Plant 3D projects in the project selection too
* New: Separators and column width in the query user interface will be saved too
* Change: Documentation
#### Version 1.5 (06.09.2009)
* New: Network licensing
#### Version 1.4 (11.08.2009)
* New: Updated to DevExpress 9.1.5.
#### Version 1.3 (09.05.2009)
* New: Added support for AutoCAD® P\&ID 2010.
#### Version 1.2 (27.02.2009)
* Bug fix: when preview or print reports with option one/obj or one/dwg only the first report was generated
* Bug fix: when switching between "Drawings" and "PID Classes" the previously selected classes were lost
* Bug fix: folder structure was not displayed correctly in some cases
* Bug fix: when using parameters in the report designer, the value of the parameter wasn't shown in preview or print.
#### Version 1.1 (21.02.2009)
* New: Updated to DevExpress 8.3.4
#### Version 1.0 (19.01.2009)
* First Version to sell.