Due to using the internal SymbolAndStyleDwg database of Plant 3D, inserting symbols which contained attributes (e.g., Instrument Symbols) into a P&ID drawing didn't show the attributes. We use a different method now.

If you already have inserted symbols where the attributes are missing you can follow this workaround:

1.Have the drawing with the missing attributes open

2.Open Project Setup

3.Select a P&ID class with a symbol

4.Edit the block of the symbol

5.Close block editor without making any change

6.Close Project Setup with OK

You will now see the attributes again.
 

A new renumbering function was added to help renumbering objects in P&ID and 3D. Typically, but not limited to, renumber a property value used in a Tag Format.

See: Renumber
 

You can now build an absolute path for example when using the SymbolsPalette.

See: Get Project Path
 

You can now calculate the GraphicalStyleName. This can be useful if the Graphical Style Name depends on some other values and Plant 3D Symbol List property is not available or wouldn't help.
 

We migrated the Calculation dialog to use DevExpress. This also allows filtering in the class tree and the Property list.

When selecting Boolean type for Assembly Class' Custom Properties the settings user interface show a checkbox now.

The Signal Line Group and Signal Line Segment properties weren't created (if missing) together with the Pipe Line Group and Pipe Line Segments. Now they are. The dialog was also updated to show more detailed information about which properties for what classes will be created.

When checking/unchecking the boxes for the Assign Tag dialog, the state of the box is not only propagated to the sub classes, but you can also see whether the state of the check box is inherited in the sub class or not.

The main user interfaces of PlantLink and the PlantExpressTools Calculation function showed a light background color when AutoCAD was set to Dark Theme.

When using Close Project in PlantProjectManager an error occurred. This is actually a PlantLink bug triggered by PlantExpressTools' PlantProjectManager.

When using %USERPROFILE% as a variable for relative paths the variable isn't evaluated correctly.

When using multiple independent Assembly classes (no stacked Assemblies) then the acquisitions worked only for one Assembly, but not the others.

When importing a calculation file and then clicking on the Refresh button, the *.calc file was correctly checked in, but so was the CalculationConfiguration.Collection.xml, but the file has to be kept checked out while the Calculation dialog is still open.

An error in the Calculation dialog appeared when clicking the Refresh button after importing a *.calc file after another *.calc file was already imported.

If a Collaboration project was backed-up the DocumentServer.slnk file still exists which led PlantExpressTools think it is still a Collaboration project.
 

If the CoordinatesSettings.xml was deleted through Project Manager or PlantProjectManager, the file was recreated when opening and closing the PlantExpressTools Settings dialog, but the file was not added to the MISC database and therefore it didn't appear in Project Manager or PlantProjectManager.

If the AssignTagProperties.xml was deleted through Project Manager or PlantProjectManager, the file was recreated when opening and closing the PlantExpressTools Settings dialog, but the file was not added to the MISC database and therefore it didn't appear in Project Manager or PlantProjectManager.

If the PropertiesPaletteConfiguration.xml was deleted through Project Manager or PlantProjectManager, the file was recreated when opening and closing the PlantExpressTools Settings dialog, but the file was not added to the MISC database and therefore it didn't appear in Project Manager or PlantProjectManager.

If the FromToSettings.xml was deleted through Project Manager or PlantProjectManager, the file was recreated when opening and closing the PlantExpressTools Settings dialog, but the file was not added to the MISC database and therefore it didn't appear in Project Manager or PlantProjectManager.

When opening a project the settings from the FromToSettings.xml weren't loaded and therefore could led to the wrong property names.

When making changes to the From/To settings, the changes weren't used right away and therefore could led to the wrong property names.
 

The project must first be checked out in order to create the properties for the From/To function when using a Collaboration project.
 

When AttributeFlow gets triggered by copying values through OPC Manager the Port properties won't be updated through AttributeFlow.
 

When opening the Rule-Based Block Insert dialog an error message appeared. This was due to the change to a new method of reading xlsx files in version 8.0.0.4046.

Some Task Dialogs like OPC Manager's Disconnect dialog had to long texts which led to wrongfully formatted dialog.

Now ... will be shown in case the text is to long.

Lines in the Log File of PlantExpressTools were shown suggesting that the bolt catalog and the Plant 3D Reference Catalog were downloaded
 

INFO 09/09/2024 11:52:05,942 ACPlantConsult.PlantProjectCollaboration.CollaborationUtils ==> Download --> [1] File <C:\ProgramData\ACPlant Consult\PlantTools\PlantExpressTools\BoltCalculation\BoltCatalog.db> downloaded

 
INFO 09/09/2024 11:52:05,949 ACPlantConsult.PlantProjectCollaboration.CollaborationUtils ==> Download --> [1] File <C:\AutoCAD Plant 3D 2024 Content\CPak ASME\ASME Pipes and Fittings Catalog.pcat> downloaded
 

Lines in the Log File of PlantExpressTools were shown suggesting that the bolt catalog and the Plant 3D Reference Catalog were downloaded

When opening a Collaboration project only the LegendCOnfiguration.Collection.xml was downloaded, but not the referenced lgdcf files and subsequently also not the referenced drawings.

When closing the List function user interface after editing a List configuration the progress panel appears and then gets stuck.
 

Enabling and disabling a List configuration doesn't instantly change the status in the lgdcf file as it is done with other functions (e.g., enabling/disabling a calculation).
 

The title of the List Function shows the title of PlantSpecDriven.

If the Default Value for Boolean properties is not set to True or False, the property was created as String and the following properties weren't created.

The control for the Default Value in the settings when selecting Boolean was adapted to only allow True or False values (PT-4368). However, if there is still a wrong value in the Assemblies.xml, then the Default  Value will be automatically False.

The 2 columns have to be swapped and the header of Options: has to be Option without the colon.

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.
 

PlantClashDetection can now be found in the PlantExpressTools Ribbon as Clash Detection and is therefore part of the PlantExpressTools product. PlantClashDetection will not be offered as a stand-alone product anymore.

Since creating the images for the SymbolsPalette took only a few seconds at first use we decided to not store the images anymore to avoid the few seconds of loading time next time you use the SymbolsPalette. The images will be stored in memory as long as the Plant 3D session is running.

This ensures, that the images shown are always the latest version of the project setup.
 

When exporting project setup to a XLSX file, the file will be opened right after the export will have been completed.
 

PlantExpressTools and PlantDataManager have a more modern user interface for the Calculation configurations.

When switching between light and dark color schemes in Plant 3D the ribbon images weren't updated right away.
 

The Plant 3D Reference Catalog set in the Bolt Calculation settings will be added to the MISC database even if the catalog is not withing the project. Now the catalog will be added only if within the project. This is especially important for Collaboration projects, because if a file is not within the project, but added to the MISC database, such a project cannot be shared.
 

When opening PlantProjectSetup the BoltCalculation.xml gets checked out, but not checked in when closing PlantProjectSetup.
 

The BoltCalculation.xml doesn't get downloaded when the project gets opened. If the Bolt Catalog and/or the Plant 3D Reference Catalog are also within the project's folder structure, then those files also don't get downloaded.
 

When selecting the option to Open, Propagate, and Close the connected drawing after AttributeFlow did its job, the drawing stayed open.

This is also in combination with PlantExpressTools OPC Manager.
 

When importing project setup and an existing property should get a different Selection List assigned to, then this fails.
 

When changing size or spec on a line segment connected to another drawing, then the dialog asking about whether to propagate the data appeared, but then nothing happened. The connected drawing wasn't opened.

This is also in combination with PlantExpressTools OPC Manager.
 

PlantExpressTools and PlantSpecDriven created an ACPlantTools folder in the documents folder.
 

When having referenced files used by a Selection List configuration and these referenced files were stored in the Related Files folder, then these referenced files appeared under Related Files\ACPlantTools\Related Files\[FILENAME]. This is not only irritating, but prevents sharing such a project with ACC. Now the referenced files will appear directly under Related Files in Project Manager or PlantProjectManager.

When having referenced files used by a List Function configuration and these referenced files were stored in the Related Files folder, then these referenced files appeared under Related Files\ACPlantTools\Related Files\[FILENAME]. This is not only irritating, but prevents sharing such a project with ACC. Now the referenced files will appear directly under Related Files in Project Manager or PlantProjectManager.

When enabling or disabling Selection List configurations, the slcf files don't get checked out and in again which prevents the changing of the state in the file.
 

An error dialog appears when trying to update Bolts from the context menu of PlantProjectManager.
 

When downloading a Collaboration project the first time, the BoltCalculation.xml gets checked out and stays checked out. If the Bolt Catalog and/or the Plant 3D Reference Catalog is also in the project's folder structure, these files will also be checked out and stay checked out.
 

The Rename/Copy function was adapted for Collaboration Projects. However, renaming Collaboration Projects is not possible only Copying.

Collaboration Project will by copied by first creating a project backup under the new name and then shared again. You can use the same project name in case you want to copy the project to a different Collaboration Account/Project.

The DWG Export function will download all files which need to be exported in case they are not available yet in the local work folder.

The dialog which informed about pending From/To tasks can be suppressed now. This is very useful, when you import data because of changes being made in PlantDataManager and a lot of drawings will be opened and this dialog appears every time.

You can enable to the dialog again in the PlantExpressTools settings under the From/To tab.

If the checkbox Close AutoCAD Plant 3D after the project has been created is enabled, the dialog #00427 will not appear. This way Plant 3D gets closed without the need for user interaction.

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.
 

At some point in a previous version the two controls got disabled.

The AQAPTRemoveDuplicateACPlantToolsFolder function also removed linked nodes which had nothing to do with PlantTools configuration files.
 

When deleting the Assembly object which has objects in it, the mapped property in the objects won’t be deleted.

The status of the checkbox for assemblies isn’t stored in the Assemblies,xml.

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.

PlantTools for Collaboration projects are available only for AutoCAD Plant 3D 2023 or higher. This is due to the fact, that the API PlantTools rely on were improved in 2023.

Some functions may still work, but it is not supported. Make sure you install Plant 3D 2023 or higher.

The BoltCalculation.xml, BoltCatalog.db and Plant 3D Reference Catalog will be check in/out or downloaded when using Collaboration projects. The user doesn't need to manage the file manually anymore.

Update bolts for a drawing a folder or a category in PlantProjectManager will check out the drawings before opening them.
 

When using the AttributeFlow Task List the xml file with the pending tasks will be handled also when using Collaboration projects. This also includes handling of the AttributeFlow through OPC Manager in PlantExpressToools.
 

Project Setup will be checked out and in when adding properties used by the From/To function. If drawings need to get opened because of line segments linked by Off-Page Connectors, the drawings will be downloaded if needed and opened in read-only mode.
 

Storing unfinished tasks in a task list isn't necessary. The From/To function writes unresolved Off-Page Connector in the From/To properties. Based on that information it is possible to retrieve from the database if there are pending changes when opening a drawing or when using the Task List button in the PlantExpressTools ribbon for the whole project.
 

The OPCSettings.xml will be check in/out or downloaded when using Collaboration projects. The user doesn't need to manage the file manually anymore.

All functions for connecting/disconnecting will check out/in the drawing files if needed.
 

When selecting a symbol from the SymbolsPalette, the symbol can be continuously inserted without the need of using the Space Bar or Return key. This is especially interesting when using PlantSpecDriven when PlantSpecDriven inserts also flanges. In this case the selected valve symbols will still be next to insert. Previously when using the spcae bar, the flange symbol was next to be inserted.
 

In case the \ACPlantTools\PlantExpressTools\ClassesAndProperties\PropertiesPaletteConfiguration.xml file contains, properties, classes, groups, or tabs which aren't used anymore in the project, then the user will get a dialog when opening the PropertiesPalette settings or when having the PropertiesPalette open and selecting an object in the drawing or the data grid.

The settings can be changed if needed.

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.
 

When switching between AutoCAD Workspaces the PlantTools palettes weren't restored to the previous setting. For example, if a palette was open before, it may be closed after the switch. Now the palettes will be opened again if they were open before.

This applies to the following Palettes:

1.PlantSpecDriven Tree

2.PlantSpecDriven - Inconsistency

3.PlantDataManager Plugin - Data Import

4.PlantExpressTools - PlantProjectManager

5.PlantExpressTools - PropertiesPalette

6.PlantExpressTools - SymbolsPalette
 

The PET Settings Settings dialog can be resized now in order to make it easier to manager the moving around of the selected properties.

The local setting are moved to the project. The new file \ACPlantTools\PlantExpressTools\FromTo\FromToSettings.xml will also be handled for Collaboration projects.
 

The line segments with an OPC which is not yet connected to another OPC will not marked with unresolved From/To data (previously unresolved Off-Page Connector), because the From/To properties cannot be resolved, because they are not connected. However, with the new method implemented with PT-2473 the user would always be notified about unresolved From/To data, but those of unconnected OPCs cannot be resolved.
 

We updated the several dialogs of the From/To function.

This the the new dialog, when the From/To Update gets executed in a drawing.

This dialog appears (unless suppressed) when opening a drawing and there are pending (unresolved) From/To values in the Line Segments. The dialog can be suppressed. In the PlantExpressTools Settings dialog From/To tab the dialog can be made available again.

This dialog appears if the user wants to update ALL pending (unresolved) From/To values in the Line Segments.

When changing the workspace twice, the PET ribbon looks like this:

When closing the PlantExpressTools Settings dialog, the PropertiesPaletteConfiguration.xml doesn't get checked in.
 

When using the P&ID or 3D  databases as the data source file in the Selection List function, then PlantExpressTools will automatically use an internal variable for the database file.

When executing the update function...

...you get an error.

When using the Microsoft OLE DB Provider for SQL Server OLE DB Provider...

...and then you click on Views you get an error.

When using the SQL Server Native Client 11.0 provider everything works.
 

The PlantProjectSetup user interface could be shrinked to such a small size, that some controls were cut of.

When making changes to the checkboxes in the Assembly settings, the changes were saved in the Assemblies.xml, but were reset after restarting Plant 3D.

Due to a bug fix (PT-2167) in version Version 7.1.0.3289, inserting a Symbol into an Assembly, the relationship between the Symbol and the Assembly wasn't created on insert if the checkbox to do so was checked in the Assembly settings.
 

The Clean Database Synchronization button was not fully visible.

If the path to a drawing was empty in the database, the rename/copy project function showed an error dialog.
 

The BoltCatalog.db contained some wrong heights for ASME Nuts and Washers. The new catalog contains the fix.

To get these corrections into your own catalog you can export the ASME nuts and washers from the shipped catalog and import it into your own.
 

When loading a BIM project, there was an issue with the SymbolsPalette if there were also pending From/To tasks.

When the Bolt Calculation check if the Bolt Catalog contains columns which aren't in the Plant 3D reference catalog, then dialog #00279 appears. After selecting Remove columns an error appeared.

When creating a new project using the Project Manager function, then Plant 3D will create a second ACPlantTools folder.

We provide a function which removes the unneeded ACPlantTools folder. Use the following command:

AQAPTRemoveDuplicateACPlantToolsFolder
 

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.
 

We implemented a locking mechanism to prevent multiple users opening PlantExpressTools Settings or PlantProjectSetup. This applies to Collaboration and regular network projects.
 

For Collaboration projects we need to know which PlantTools settings files still need to be downloaded in case they don't yet exist locally.
 

We watch PlantTools folder and configuration files in order to recognize changes (made by another user) in those folders and files. If files change, we need to invalidate the cached PlantTools settings in the Plant 3D session to ensure, the PlantTools use the latest settings.
 

When importing csv files as Selection Lists or xls/xlsx files for Project Setup with the Ex-/Import function, we first check out the project setup, then import and then check the project setup in again.
 

Project Setup will be checked out and in when adding properties used by the Coordinate function.
 

Full integration of Selection List function and its configuration files for Collaboration projects.
 

When updating all Tags of the project, each drawing must be checked out, opened, updated and checked in again.
 

When updating all Acquisitions of the project, each drawing must be checked out, opened, updated and checked in again.
 

The LegendConfiguration.Collection.xml and all *.lgdcf files will be check in/out or downloaded when using Collaboration projects. The user doesn't need to manage the file manually anymore.
 

The files for the SymbolsPalette (SymbolsPaletteState.xml, SymbolsPaletteCategories.xml, SymbolsPaletteCustomClasses.xml) will be check in/out or downloaded when using Collaboration projects. The user doesn't need to manage the file manually anymore.

User defined images which can be used in the SymbolsPalette will also be migrated into the Images folder \ACPlantTools\PlantExpressTools\SymbolsPalette\Images when loading the project.
 

The Assemblies.xml file will be check in/out or downloaded when using Collaboration projects. The user doesn't need to manage the file manually anymore.
 

The CalculationConfiguration.Collection.xml and all *.calc files will be check in/out or downloaded when using Collaboration projects. The user doesn't need to manage the file manually anymore.
 

The AssignTagProperties.xml file will be check in/out or downloaded when using Collaboration projects. The user doesn't need to manage the file manually anymore.
 

The PropertiesPaletteConfiguration.xml file will be check in/out or downloaded when using Collaboration projects. The user doesn't need to manage the file manually anymore.
 

We now show a warning dialog in case a drawing is read-only or not checked out.

The text depends on the function being used. Here is the example when using the Coordinate function.

For Collaboration projects is a bit different.

A new toggle button is available in the SymbolsPalette to activate/deactivate the Edit Mode. Only when enabling the Edit Mode it is possible to make changes/additions to the SymbolsPalette. For example, add new Custom Classes, Folder Links, Custom Objects. If the Edit Mode is not enabled, the commands from the context menus which allow to make changes to the SymbolsPalette are not available and are not shown.

The toggle buttons to change the style, size and so so are still available and can be adjusted by every user. The same applies to the settings in the PlantExpressTools Settings dialog on the SymbolsPalette tab.

Being in Edit Mode prevents other users for making changes to any other PlantTools settings.

If Edit Mode is disabled you have a grey icon.

If enabled, the icon changes to green.

Up until now the user display name is only used when being in Class Display Name mode.

We changed in the way that the user name is used and can be set in Class Display Name and Symbol Name mode. The same user display name is used for both modes.

When toggling between Class Display Name and Symbols Name, the User Name is always used.

The settings for the Display Name the the Graphical Style Name have been removed from the Symbols tab of the PlantExpressTools settings, because they can be changed with toggle buttons in the SymbolsPalette. The path setting was also removed, because especially when using a Collaboration project the path must point to the project anyway.

The following marked settings are gone.

Now it looks like this.

We added a toggle button to the right toolbar where the user can toggle between the user-defined display name or the class/symbol name.

This way the user can always switch back to the original Class Display Name or Symbol Name to see or search for the original names.

Here the Symbols Names with using User Names:

Here the Symbols Names with not using User Names:

Here the Class Display Names with using User Names:

Here the Class Display Names with not using User Names:

When selecting a DWT file when creating a new drawing File Explorer now shows an 'AutoCAD-Application' node to quickly access the folder if the pre-defined DWT files or the AutoCAD defined folder for the DWT files.

This is how it looks in File Explorer. If you click on Template you will be send to the folder defined in the ACAD profile.

When using collaboration not all files are necessarily downloaded. Therefore we check the existing drawings in the PnPDrawings tables in order to provide a drawing name which isn't used yet. Of course, you can only be certain that a drawing name isn't used yet if you ran Refresh from Project before creating a new drawing.
 

To add an existing configuration file you can now use the Import button. This will will then be copied into the appropriate PlantTools folder, will be added to the collection file and if it is a Collaboration project, the configuration will also be checked in.

To add an existing configuration file you can now use the Import button. This will will then be copied into the appropriate PlantTools folder, will be added to the collection file and if it is a Collaboration project, the configuration will also be checked in.

To add an existing configuration file you can now use the Import button. This will will then be copied into the appropriate PlantTools folder, will be added to the collection file and if it is a Collaboration project, the configuration will also be checked in.

The Properties Dialog for folders wasn't implemented yet.

When using the Refresh button we check if all configuration files are also listed in the Collection file and if not, we added the missing configuration files.

Now the configuration files which are not in the Collection file will be deleted.

In case you want to add a existing configuration file you can now use the Import button.

When using the Refresh button we check if all configuration files are also listed in the Collection file and if not, we added the missing configuration files.

Now the configuration files which are not in the Collection file will be deleted.

In case you want to add a existing configuration file you can now use the Import button.

When using the Refresh button we check if all configuration files are also listed in the Collection file and if not, we added the missing configuration files.

Now the configuration files which are not in the Collection file will be deleted.

In case you want to add a existing configuration file you can now use the Import button.

The local setting are moved to the project. The new file \ACPlantTools\PlantExpressTools\Coordinates\CoordinatesSettings.xml will also be handled for Collaboration projects.
 

When using the Refresh button on the SymbolsPalette all SymbolsPalette Configuration files and images will be reloaded now.

The two settings were stored in the \ACPlantTools\PlantExpressTools\SymbolsPalette\SymbolsPaletteState.xml. The settings store the state of these two toggle buttons:

The new location is now in the C:\ProgramData\ACPlant Consult\PlantTools\PlantExpressTools\PlantExpressTools.xml.

When creating a new configuration for the selection list function, the SelectionListSettings.Collection.xml isn’t written when the main dialog gets closed.

The file is gets written only when you close the project and open it again and then open the main dialog again.
 

The selection list function uses the name of the selection list + the option for the selection list (e.g. Services_ClearAndImport.slcf). When creating a second configuration the file was automatically named like this: Services_ClearAndImport[1].slcf. But now the file just gets overwritten.
 

When selecting the ProcessPower.dcf or the Piping.dcf as the data source...

... an error appeared.

If a sort order was selected (A-Z or Z-A, the order was not instantly considered when selecting a class in the tree.

When changing the order of properties for the PropertiesPalette, the order was written into the PropertiesPaletteConfiguration.xml, but not instantly used. Only when reloading the project the new order was used.
 

When trying to open a drawing when using a collaboration project through PlantProjectManager failed with an error message. The same applies when trying to open a drawing Read-Only.
 

When creating a new drawing with PlantProjectManager it searched for the pre-defined DWT file in the path set in the ACAD profile and not in the path set in Project Setup.
 

When stretching line segments with flow arrows when using Assemblies, the flow arrows jumping around. Meaning the flow arrows are not where the were supposed to be. Even stretching line segments which were a copy of previous drawn line segments, the flow arrows of the original line segment was jumping around when stretching the copied line segment.
 

If the bolt calculation couldn't find suitable BoltSets or bolt parts, the Bolt Calculation always showed Bolts database xxx is not valid if though the database is perfectly fine. As soon as the issue where the Bolt Calculation could find the BoltSet or the bolt parts the issue with the invalid bolts database was also gone.

Force Undo Check Out wasn't available in PlantProjectManager in order to force a Check Out.

After a PlantExpressTools license was exported and Plant 3D restarted you cannot import or activate PlantExpressTools anymore, because of an error message when opening PlantExpressTools settings dialog.

Making changes in PlantProjectSetup for example to OPC Manager settings, will not be saved when closing PlantProjectSetup.
 

When using Copy ALL values to other Connections in OPC Manager to copy inconsistent values...

... it not only copied the inconsistent value, but all different values.

Even if the Check for Inconsistency checkbox wasn't checked.

When a new configuration for the List function is added or removed, it is not immediately saved when the dialog is closed.

When having the version/revision option enabled in PlantProjectManager and the user types in a file name and then changes the Description or changes the Created by name or switches from Set initial version to Set initial revision, then the file name was reset.

New file name:

Now changing Description and the File Name gets reset:

When using Publish from the context menu of a drawing in PlantProjectManager, you got the following error:

In some cases the system variable FILEDIA was set to 0. It was not reproducible, but it happened.

When you used Open Project in PlantProjectManager the File Selector dialog didn't open. Instead you were supposed to use the command line to enter the project path.

Now FILEDIA will be set to 1 before using Open Project and will be reset to the previous value after the fact.
 

When using Add From Tool Palette... an error appeared.

When using the From/To function the first time, the following dialog appears:

If you clicked on Cancel, the From/To function was trying to calculate the From/To data anyway. But since the properties don't exist nothing happened.

PlantTools now support AutoCAD Plant 3D 2024.

PlantTools support AutoCAD Plant 3D 2019 - 2024 now.
 

The Plant 3D Collaboration functions are available now in PlantProjectManager too.

We updated DevExpress controls and tools to the latest version 22.2.5 in all PlantTools.
 

We extended the search path to go through the following locations:

•TRUSTEDPATH

•Plant ACAD Path collection

•Plant Support Path collection

•ACAD Location
 

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

The PlantExpressTools Settings dialog use the AutoCAD Plant 3D icon whereas all other Settings dialogs from the other PlantTools don't show any icon.

After selecting a project in PlantProjectManager, the Plant 3D Project Manager got closed even if the checkbox Close AutoCAD P&ID/Plant 3D Project Manager on startup was not enabled.

When starting Plant 3D and PlantProjectManager is not supposed to be opened, then the PlantProjectManager icon is still showing an active/enabled state.

An error occurred when opening a local Collaboration project, but the project didn't exist on the Collaboration Server anymore.
 

This was a bug introduce not that long ago where the the PlantExpressTools Settings dialog write the property display name into the

\ACPlantTools\PlantExpressTools\ClassesAndProperties\AssignTagProperties.xml

instead of writing the property name itself.

Now the real property name will be written again.

There is also a migration function which replaces the Display Names with the Property Names if needed. This migration will happen as soon as you open the Assign Tag dialog and click on OK.

Then the following dialog opens. After you click Open now the PlantExpressTools Settings dialog opens which you then close with OK. This will then write the real Property Names into the AssignTagProperties.xml.

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
 

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
 

You can copy existing AutoCAD commands/AutoLISP functions from existing AutoCAD Tool Palettes onto the PlantexpressTools SymbolsPalette.

When the default symbol/block is created automatically by the Assembly function, Color, Lineweight, Linetype and Transparency now always use BYBLOCK instead of the current settings when the block was created.

We changed the methodology of searching for the NominalDiameterMap.csv file which is typically located in the C:\Program Files\Autodesk\AutoCAD 20XX\ folder. However, there are situations where the file cannot be found, because of invalid paths in the Trusted Locations.
 

Making sure, that the PlantTools ribbons in AutoCAD Plant 3D use the current language.
 

The AutoCAD language code for French Plant 3D wasn't supported in PlantTools. This effected all PlantTools.
 

When selecting a node in the tree for the Bolt Length, the Length/Weight data grid didn't show the data of the selected Bolt/Nut/Washer/AddOn standard, but from the previous selection standard.
 

When using the Line Annotation Update function:

We showed the following unclear error message if the current drawing wasn't a P&ID drawing:

Now we show a simple message in the command line.

Sometimes customers use Tag Formats which doesn't use any property. This then looks like this in the Assign tag dialog:

In such cases, the property value will be stored directly in the Tag property.

In such cases the Tag Update function we deleting the Tag property value, because the Tag couldn't be recalculated. Now we ignore such Tag Formats.
 

At some point in the past the Drag & Drop function in the Bolt Parts tree got removed. Now you can copy again by dragging and dropping.

Classes and Categories in the SymbolsPalette can now be hidden. Hidden Classes/Categories can be made visible with a separate toggle button in the left toolbar.

Function to Expand/Full Expand/Full Collapse/Collapse are available now. Options which aren't available are disabled or not shown.

User definable nodes can be created within the class structure to add your own content to the SymbolsPalette. Custom Nodes can have a hierarchical structure.

You can add Folder Links to be able to insert DWGs or Images into your drawings.

Categories can be moved up and down using Drag & Drop.

In addition to create user definable nodes you can now also create your own 'Object Items' for the right side of the SymbolsPalette.´

You can use this to add Hyper Links (URLs) to your SymbolsPalette or AutoCAD Commands or AutoLISP Code.

Added ability to rename the Display Name of the Class for the SymbolsPalette.

This will not change the Class Display Name in Project Setup. Just the displayed name in the SymbolsPalette. The displayed Symbol name cannot be changed.

Due to the new feature to change the class display name, the renaming and image specification was combined into one new dialog.

The existing 'Category Configuration' dialog now shows the used classes in grey in tree. Also hidden classes are also hidden in the tree (e.g. Hand Valve in the example image below).

Up until now, the matrix for the bavior you could expect when considering the option Override if Empty as well as using AttributeFlow of PlantSpecDriven looks like this:

We changed the behavior when using None in combination with Override if Empty which leads to this matrix now.

When connecting OPCs and PipeLineGroup or SignalLineGroup class is used, then an error appeared when the connection was done.

The reason behind it was, that there are no properties involved for Line Groups, because when connecting, the two Line groups become one. There can never be an inconsistency between a property on the two sides. When the function which gets the DisplayName was used during the connection, the error appeared, because there is no property name for which to get the DisplayName.

When starting Plant 3D and having activated the SymbolsPalette opening on startup, the SymbolsPalette gets opened, but the toggle button in the PET ribbon doesn’t show this.

Adding two new functions to the calculation function:

PTGetScriptParameter(ParameterName) – Gets the value of a specific parameter name (i.e. "H") of an object. If the parameter doesn't exist the result will be NULL. The type is float/double

PTGetAllScriptParameters() – Gets all parameter of an object (i,e, “B1=14,B2=14,D1=21.3,D2=21.3,D3=0,H1=95,H2=95,L=130,LS=0,OF=0,W1=0,W2=0,DO=0,HA=90,LA=130”. The type is string. Valves may be treated differently, because the are made out of a Body and Actuator.
 

If the mapping grid shows a row for which an AttributeFlow task exists, then the task can be remove by using the context menu and select 'Cancel Task for current Property.

A new column was added to the OPC Mapping settings where a property with no value will be overridden with the other other connection's property value (if it is not empty) independent of the Drag & Drop direction. Or when independent when using "Outgoing" or "Incoming".

The matrix below shows what the result will be when using this option or not. Also in combination with AttributeFlow.

When disconnecting an OPC for which there are AttributeFlow tasks, those tasks will be removed from the task list. If no tasks are left, then the file will be deleted.
 

With this feature you can edit and overwrite values in the mapping grid within OPC Manager.
 

There are more options when disconnecting OPCs. This also requires the handling of a line group continuing over multiple drawings as in this example where all line segments in all 3 DWGs belong to the same line group.

When you disconnect the incoming OPC in DWG 2 you now get three options. The first one is new.

"Create new Line Group for all disconnected Line Segments" will create a new Line Group for all Line Segments from the incoming OPC in DWG 2 till the outgoing OPC in DWG 3.

"Create new Line Group for single disconnected Line Segment" will create a new Line Group only for the Line Segment which is connected to the disconnected incoming OPC in DWG 2. All other Line Segments in DWG 2 and DWG 3 will still belong to the same Line Group from DWG 1.

"Keep the same Line Group" will not create a new Line Group and therefore all Line Segments in all 3 DWGs will still be part of the same Line Group.

In PlantProjectSetup the option has now a dropdown list where the selected option is stored in case you do not want to see this message again.

The AttributeFlowTaskList.xml file is still using PnPIDs instead of PnPGUIDs which is a problem when using Vault or Collaboration projects.
 

The OPC Manager trees collapse after you select any option of dialog #01167.

When copying a single symbol from one Assembly into another with the COPY command it happened, that the after the symbol was copied, that then multiple symbols were on the mouse pointer for another copy. Now we also consider the COPY command not just the MOVE command when the check box in the PET Settings-->Assemblies is enabled.

With a fresh Plant 3D installation, the node to PlantTools is also missing in the Registry. In this case an error appears when you open PET Settings the first time. THe missing entry in the Registry is:

Computer\HKEY_CURRENT_USER\Software\ACPlant Consult\PlantTools
 

The info box of PlantExpressTools was sometimes hidden behind the PlantExpressTools Settings dialog.

Although the P3dLineGroup class could be selected for the calculation it was never tested.

When editing the properties of the 3D line group used in a calculation an error appeared in the command line and the property isn’t calculated.

Failed to update calculated property: ObjectDoesNotHaveLink (P3D-P3dLineGroup-InsulationSpec, 589, InsulationType)

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.
 

If an OPC has a user state and you can and want to set it to 'Unconnected'...

... then the LinkStatus showed 'Unconnected' instead of 'Unconnected_Userdefined'. This led to the fact, that the OPC appeared in blue and in both trees.

When creating a new user state, then the symbol wouldn't change its color after assigning this new status to the OPC.

When adding or changing an existing node expression and then close PlantProjectSetup, the nodes in OPC Manager aren’t updated automatically. I have to click on Refresh.
 

It could happen, that when reconnecting OPCs, that Plant 3D crashed. This was due to the fact, the the drawing was still locked by the Viewed in OPC Manager.
 

When drag an drop the Incoming Line Segment to the Outgoing Line Segment, the defined mapping direction is ignored.

The ‘Incoming Line Segment’ mapping direction is ignored. Instead 'Outgoing Line Segment is used.

If you have a user defined state in OPC Manager and then you delete this state in OPC Manager's settings Plant 3D crashed. Now the state will be updated from the user state to whatever OPC Manager determines.

When connecting OPCs the settings for 'Do not show this message again' and the selected option where stored and shown in the PlantSpecDriven settings, but not then considered and shown in OPC Manager.

The same issue applied when executing existing AttributeFlow Task through the mapping grid.

Up until now OPC Manager didn't use the display names of classes and properties.

Before:

Now:

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.
 

The SymbolsPalette shows a new toggle button to switch between showing only the symbol defined under GrphicalStyleName in project setup and all class symbols now.

This icon shows only the symbol as defined under 'Graphical Style Name' for the class in Project Setup.

This icon shows all symbols defined for a class.

Previously you had to change this in the PlantExpressTools Settings --> Symbols tab.

The SymbolsPalette collapses the tree when clearing the filter control now.

The whole tree is collapsed except the branch of the node you selected before. This way you don't need to expand the tree again to the class you were looking for.

The SymbolsPalette shows a new toggle button to switch between Class Display Name and the Symbol Name now.

This icon uses the Class Display Name.

This icon uses the Symbol Name.

Previously you had to change this in the PlantExpressTools Settings --> Symbols tab.

The SymbolsPalette shows the status at the hide/show toggle button at the toolbar now.

This icon indicates that the hidden symbols will not be shown.

This icon indicates that the hidden symbols will be shown (with a box around them).

The SymbolsPalette shows the current view style at the toolbar now.

Icons Only

Icon with Text

List View

The SymbolsPalette shows the current sort order at the toolbar now.

None (The symbols appear in order of the classes in Project Setup).

A-Z

Z-A

When making a right-click on a hidden symbol the context menu shows 'Show' now instead of 'Unhide'.

When switching to the Categories View in SymbolsPalette, then no categories are shown.

When creating a new category...

... the header of the class list shows a wrong text.

When selecting 'Hide' from the context menu of a symbol to hide a symbol from the SymbolsPalette, this state wasn't stored, because if a missing SymbolsPaletteState.xml at new projects.

Now Hidden:

Now Shown:

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.

The PropertiesPalette of PlantExpressTools and PlantDataManager sometimes showed a tab twice.

An error appeared when making a right click on a drawing category node if the [PP]\ACPlantTools\PlantExpressTools\BoltCalculation\BoltCalculation.xml is of file size 0.

If an Selection List configuration file is invalid, because the settings do not work with the current project configuration, then you will see an error message as a tooltip. The State will also be set to disabled. The configuration cannot be enabled anymore. It must be corrected by using Edit or with a double-click on the configuration.

When creating a calculation for 3D the ClassType in the *.calc file is set to None.

This leads to an error and the calculation won't be executed.

When opening the PlantExpressTools settings and selecting the 'Assemblies' tab, the Assembly Class Name and Display Name was not read from the Assemblies.xml, but used from the default values. In addition, the Assmblies.xml was overwritten with the Class Name and Display Name of the default values.
 

When using the Filter Expression Editor for either Rule-Based Block Insert or OPC Manager, the dropdown lists would expand and instantly collapse making it impossible to select anything.

When a property of a Connectors class is used, the property wasn't mapped.

Trying to copy the value of a Connector property failed.

If you have line segments which are not connected to another line or symbol, then clicking on a node on the Incoming side will show the the connection lines on the wrong node.

When opening a project which is setup for PlantSpecDriven, but the current project wasn't setup for PlantSpecDriven, then the following error appeared, because OPC Manager is also using PlantSepcDriven's AttributeFlow.

When switching to another project somtimes the following error appeared, because the path to the PlantSpecDriven folder wasn't reset. The path is used OPC Manager in case the project is using PlantSpecDriven too.

When switching from one Connector class to another where the Connector classes have Filter Expressions, the expressions didn't get stored and restored while switching.

When trying to create a new list configuration, the wizard shows error starting on page 3. The reason was, no option was set as a default.

If OPC Manager and a drawing is open in the current project, and then another project is opened, then OPC Manager is flickering. Most noticable with the connec tion lines between the trees. When you try to close OPC Manager you get an error.

If copying a symbol with an annotation, the the annotation of the new symbol will be moved to the insertion point of the symbol. This was due to an issue in the Assembly function even if the project doesn't use Assemblies.

When having Assemblies within Assemblies and using mapping instead of acquisitions, then the symbols or lines weren't always related to the correct Assembly.

If symbol names contains a & we had to handle it differently. Otherwise it created an error.

PlantExpressTools always check if the pipe specs need to be updated if the Bolt Calculation is activated for a project. Now PlantExpressTools check the pipe specs only once and then store the info, that the pipe specs have been check. This avoids the need for checking the pipe specs with every project load.

In case you make changes to the pipe specs or add pipe specs to the project, you then simply deactivate the bolt calculation, click on Apply and then activate again. This forces a one time check of the pipe specs.

In preparation of supporting BIM360 projects we renamed the Settings.ppm to CategorySettings.xml. The file is used with PlantProjectManager. However, with existing Settings.ppm files the renaming failed.

When changing the state of a check box in the 'Use in Assign Tag' column, the change of the state wasn't stored.

Sometimes OPC Manager showed the drawing file extension in the trees.

No we use the file name without extension in case PlantProjectManager hasn't calculated the file name yet.
 

When connecting OPCs with Unknown Flow Direction, the trees are empty after the connection has been created.
 

If there is an inconsistency between OPCs with Unknown Flow Direction the inconsistency isn't shown correctly in the tree and the data grid.
 

If the bolt calculation loads data from the bolt catalog which needs more time than 0.5 seconds a progress panel is shown.

In addition PlantProjectSetup will open faster.
 

If the folder PnPPersistentCache or its content gets deleted (e.g. by PnPLocalDataCachePurger.exe), an existing AttributeFlow Task Lists gets deleted on project open.

This is due to the fact, that the deletion of the local data cache results in NULL values for connected Off-Page Connectors. Then the IDs in the task list will be marked as invalid (not needed anymore) and the whole task list gets deleted.
 

It happened, that the connection between flanged parts got lost.

Initially Plant 3D will insert its BoltSet.

But after the PlantExressTools Bolt Calculation substituted the original BoltSet with the PlantExpressTools BoltSet or Single Bolt Parts, the connection got lost.

The reason was, that sometimes the pipe spec contains multiple suitable gaskets. We always used the first one handed over to the bolt calculation. But in same cases, that wasn't the correct gasket which lead to the connection loss. Now the Bolt Calculation uses the same gasket which was inserted before the Bolt Calculation function substituted the original BoltSet.
 

With OPC Manager disabled, the icon in the PlantExpressTools ribbon is disabled.

When entering and closing the PlantExpressTools settings dialog, the icon gets disabled although OPC Manager is still disabled.

When enabling/disabling OPC Manager in PlantProjectManager, the icon status in the PlantExpressTools wasn't set correctly.

Because OPC Manager is also using PlantSpecDriven's AttributeFlow, it resulted in issues with the Plant 3D ribbons in case the PlantSpecDriven folder didn't exist under the \ACPlantTools folder.

Users saw this because of an empty P&ID Painter Style or showing imperial sizes even in metric projects.

The menu item 'Set Prioritized Bolt Definition Part' was still enabled even with disabled bolt calculation.

PlantProjectManager gets reloaded at workspace change but not refreshed. This resulted in only the project node being visible.
 

With the last release we reformatted the \ACPlantTools\PlantExpressTools\ClassesAndProperties\AssignTagProperties.xml and \ACPlantTools\PlantExpressTools\ClassesAndProperties\PropertiesPaletteConfiguration.xml files and inserted a version number in those files. However, the function was faulty which led to wrong data in the XML files which then cause an empty PlantExpressTools and PlantDataManager Properties Palette as well as an error when opening the PlantExpressTools Settings or the Properties Palette Settings in PlantDataManager.

If you already opened the PlantExpressTools Settings with PlantExpressTools 6.0.0.2267 you have to update to this latest PlantExpressTools and PlantDataManager version and restore the two xml files from another project which you haven't opened yet.
 

In preparation of adapting PlantTools for Collaboration projects (BIM360/ACC) we started to add PlantTools' project related configuration files under the 'Related Files' in Project Manager. However, the files are filtered out of PlantProjectManager.

We created a White Paper which describes how you can make use of the configuration files in Project Manager.

PlantTools Configuration Files with Collaboration Projects

PlantTools now support AutoCAD Plant 3D 2023.

PlantTools support AutoCAD Plant 3D 2018 - 2023 now.
 

If the start or end of an arrow line cannot be shown because of a filtered tree, the color of the arrow line will change to orange.

The filtering can be through text filtering (see image below), or filtering by connection status (the colored dot in front of the node), or through the activated filter button.

If the arrow line is still white but cut off at the top or bottom, the node is not filtered, but just outside the scope of the tree view. If you scroll up/down the node will appear.

The PnPGuid property is now also shown in the PropertiesPalettes in PlantExpressTools and PlantDataManager. This is the globally unique identifier used by Plant 3D and now PlantTools and is especially important with BIM360/ACC and Vault projects., because in those cases the PnPID isn't reliable anymore.

We updated DevExpress controls and tools to the latest version 21.2.6 in all PlantTools.
 

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
 

Due to the changes made with PT-1467 the change log database will also be switched from PET_GUID to PnPGuid. Existing records in the database will be migrated as soon as the change log function will create additional rows in the change log database. Until then the PlantExpressTools PropertiesPalette will use the PET_GUID.

In case you want to migrate all rows in the change log database to use PnPGuid you can simply open the project once in PlantDataManager. Then PlantExpressTools doesn't need to migrate anymore.
 

When using Assemblies within Assemblies PlantExpressTools used a simplified boundary box for the Assemblies to know which Assemblies is within which Assembly. However, in complex polyline boundaries, this could lead to a wrong result. Now the Assembly function uses the vertices of the polyline to determine which Assembly is within which Assembly.
 

The reason for this bug is that whenever the PropertiesPalette is displayed for an object, it is created but not disposed after that, the surviving objects accumulate in the memory over time and pass the Windows limit.

When using a Plant 3D catalog where the NominalDiameter/NimonalUnit is null (e.g. Actuators), then error dialog #00368 appeared.

The reason for this bug is that whenever the PropertiesPalette is displayed for an object, it is created but not disposed after that, the surviving objects accumulate in the memory over time and pass the Windows limit.
 

For example, Raster-Design uses relative URIs for the ribbons which caused a FATAL ERROR when hovering over a button in the Raster-Design ribbon.
 

In case of switching to another project, copying/cutting/pasting objects between Assemblies didn't update the objects.
 

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)
 

When copying or moving P&ID objects from one Assembly to others (or outside of any Assembly) with CTRL+C/CTRL+X and CTRL+V, the mapped properties are now updated.
 

A general improvement of the performance when updating calculations in a drawing. Either my executing the update command from the PlantExpressTools ribbon or On Drawing Save.

Because of duplicate PnPIDs in ACPProcessPower and ProcessPower databases the migration failed.
 

Cleanup 'temporary' exported files too, if there was no DWG open (if called from PlantProjectManager context menu).

Cleanup takes care for cross referenced files (DWG A xrefed in DWG B, DWG B xrefed in DWG A) and do not remove DWGs which are 'selected for export'.
 

When exporting the project setup, the status of the 'Read-Only' column is not exported. It is always exported FALSE.

When copying an Assembly with COPY AutoCAD Plant 3D crashes without warning.
 

When copying an Assembly with COPY AutoCAD Plant 3D crashes without warning.
 

When editing drawing properties in Project Manager or PlantProjectManager it took very long.
 

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.
 

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:

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.
 

When trying to export the classes of a project which has the Not-Place Object tables in the ProcessPower.dcf, the export fails.

Resulting in the error dialog.

When being on the “Project Setup Export” page and then click on “Previous” and the “Next” the 4 main classes are added again.

When trying to delete/rename the ACPProject.db is ws still locked even if the project was closed or changed to another project in Plant 3D.

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.

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.

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.
 

OPC Manager is now able to recognize if the project is setup for PlantSpecDriven and its AttributeFlow.

If you connect you will see this dialog which PlantSpecDriven users are familiar with.

If tasks are stored in the PlantSpecDriven Task List you can see pending tasks in OPC Manager.

You can also open the PlantSpecDriven Task List dialog from within OPC Manager.

And you can execute all stored Tasks through the context menu of any drawing node.

Since there are more and more different types of conflicts, you can filter for all conflicts with "Show all Conflicts".

You can disable the viewer within the OPC Manager with a new toggle button in the toolbar.

Then the Viewer will disappear. The advantage is, that drawings aren't locked anymore when shown in the viewer.

When entering or pasting a string value longer than the defined length of the property database field (typically 255 characters), we show a waring icon with a tooltip to let you know, that this isn't possible.

There can be cases where the bolt calculation leaves bolt parts in the 3D database (Piping.dcf). Which can lead to wrong Bill of Materials.

When using the AUDITPROJECT command from the PlantProjectManager those orphaned bolt parts will be removed. You can also run the AQAPLANTTOOLSAUDIT command separately.

When using AUDITPROJECT from the regular Project Manager or from the command line you have to run´AQAPLANTTOOLSAUDIT separately.

At the end of the audit you may see a line like this: 17 not referenced PlantTool bolt data rows have been removed from the project.
 

We now store the single bolt part in the Weight property, because Plant 3D is using this value for the BOM in isometric drawing and automatically multiplies it with the quantity. Since we already wrote the total weight in the property, the weight in the isometric drawing was to big.

We created an additional property "Total Weight" where we store the total weight of the bolt part (Weight x Number In Set).

When changing properties in the Properties Palette in PlantDataManager or PlantExpressTools which then triggers an update of other properties, these triggered changes weren't instantly shown when selecing another tab in the Properties Palette.

For example: The change in Flow Speed triggered several calculations and a link configuration which results in the selection of Size 65 on the "FlowData" tab.

When selecting the "Basics" tab you instantly see the new values.

When substituting parts of a flanged connection (including the connector itself), the bolt calculation gets triggered now and updates the bolt set or bolt parts.
 

When the bolt calculation is activated and the bolt calculation required to update the pipe spec we used the wrong style for the progres bar.

No it looks like all other progress bars PlantTools are using.

When connecting with OPC Manager the From/To values in the connected line segments weren't always updated.

In addition, multi-connections are also handled properly now. If you have a 1:n connection you will see the multiple target Tags under To. Likewise, you will see multiple source Tags under From when having a n:1 connection.

Silent exceptions where thrown when the Properties Palette in PDM or PET tried to convert MM or IN for natural sorting.

Although the was no error dialog (hence silent exceptions), but it caused slowness in the PDM/PET Properties Palette.
 

It was possible to select the same property of a class multiple times which can of course lead to conflicting settings and therefore results.

Special Valves with Wafer and Flange End Codes weren't handled correctly.

The bolt calculation didn't always get the correct equipment nozzle when calculating the bolts for a flanged nozzle connection.
 

When enabling or disabling the checkbox for updating the bolt on drawing save, the status of the checkbox wasn't saved.

When having multiple PlantTools Plugins (PlantClashDetection, PlantDataManager Plugin, PlantExpressTools, PlantLink, PlantSpecDriven, PlantSync) installed and they are set for different languages then Plant 3D crashed if the tooltips for the PlantTools ribbon buttons are supposed to be shown.
 

In some PlantTools the URL to the online documentation pointed to the old location.
 

When using OPC Manager and connect, disconnect or map property values, then changes will happen. Those changes will be written in the Change Log database instantly as soon as they happen, to ensure, that those changes are logged even if the drawings aren't opened by OPC Manager.
 

The Mapping columns was replaced with a dropdown list where you can When automatically mapping property values when connecting OPCs you can now pre-define the order of the propagation of the property values. The Mapping Direction can be set for each property independently.

You can choose:

1.None
Automatic Mapping is deactivated and the user will use copy/copy ALL in OPC Manager.

2.Drag & Drop Direction
This is the typical and default way to define the direction the values should be propagated by using drag & drop. Meaning the values will be copied from the node you drag into the node you drop onto.

3.Outgoing Line Segment
Here the values flow from the outgoing OPC/Line Segment to the incoming. The drag & drop direction has no influence.

4.Incoming Line Segment
Here the values flow from the incoming OPC/Line Segment to the outgoing. The drag & drop direction has no influence.

PipeLineGroup and SignalLineGroup can be selected only once, because after the connection the two Pipe/SignalLineGroups become one. Therefore the Mapping Direction is handled the same for each property. Also None isn't available, because the two Pipe/SignalLineGroups become one and therefore the mapping is instantly. You can influence only the direction.

The Calculation function in PlantExpressTools and PlantDataManager allow using project and drawing properties now. This eliminates the need for acquisitions.

If you have Off-Page Connectors which just go in and right back out, the From/To Function ran into issues.

When editing a list configuration, the user interface doesn't go to page 5 when clicking on 'Next' on page 4.

When having an expression for a property in PET/PDM calculation UI and then switch to another class and then back again, the expression is gone.
 

When using the Flip grip with the bolt calculation activated, Plant 3D crashed.

Now Plant 3D doesn't crash anymore and the bolt will be recalculated after flipping the valve.
 

When opening a drawing one of the two error messages appeared.

This was an unexpected return value to out code which creates the GUIDs for the PET_GUID property when opening a drawing.
 

When executing 'Store changes in Change Log' it was necessary to open each drawing (if not already open) and then gather and write the changes to the Change Log database. Now the changes will be gathered and written without the need of opening the drawings. Multi-Selecting drawing is also possible.

In addition, the handling of acquired properties has been improved.
 

It was already possible to update Tags or Acquisitions in the whole project. However, this required opening each drawing to update the Tags or Acquisitions. Now PlantExpressTools can update Tags or Acquisitions for the whole project without even opening the drawings.

When you click on the 'Update Tags in Project'...

... you are asked whether to update the P&ID Tags or 3D Tags.

Then all drawing (P&ID or 3D) will be updated without being opened. You see the name of the drawing which is currently updated in the Progress Panel.

When you execute "Update Acquisitions in Project"...

... you are again asked to select either P&ID or 3D.

You will then also see the Progress Panel with the drawing currently being processed.

The "Tags/Acquisitions Update" tab has been removed from the PlantExpressTools settings.

When you select a drawing or OPC node in one of the trees, the drawing is shown/loaded into the viewer at the bottom right side of the user interface. This locks the drawing and other users cannot open the drawing.

You can now unlock the drawing by clicking in the area between the trees. Now the drawing is accessible for read-write access.

There is an additional filter option combining the Inconsistencies and Flow Direction Conflict into one filter. This allows an overview of all issues with OPCs and Line Segments.

Up until now, only the PlantExpressTools Change Log function created an additional property "PET_GUID". Since more and more PlantTools and functions require this property, the property will now be created on project load if it doesn't exist yet.

It will be created for all 'Base Classes' like Pipe Line Group, Signal Line Group, Engineering Items, and Non Engineering Items. It will now also be created for 3D (P3d Line Group, Piping and Equipment, Steel Structure, and Pulled Pipe Bend.

The PET_GUID will be filled (if empty) on drawing load.

The PET_GUID will also be filled right away as soon as an object is created. In addition of filling the PET_GUID with a new value if PET_GUID is empty, there are two rules which apply:

1.Copying (copy, array, mirror, CTRL+C/CTRL+V, using grips for copying, and more)
The copied objects will get a new PET_GUID because not two objects can have the same GUID.

2.Move (move, using grips for moving, rotate, CTRL+X/CTRL+V, and more)
The moved objects will keep their GUID.

The two rules apply also when copying and moving between drawings.
 

The performance of PPM when expanding the tree nodes is slow. Especially for customers who use SQL Server. This was due to the following improvements:

1. Improve performance by caching the list of categorized properties for each category type so we do not need to fetch properties too often.

2. Writing back the calculated node texts in bulk and not node by node.

3. Handling exception for existing DWL/DWL2 files.

When opening a drawing, the change log function will now only load the change history of the current drawing and the history in case a symbol of the current drawing was previously in another drawing. This reduces the amount of data the change log is then comparing against, when determining the changes.
 

If one of the triggers of the Change Log starts the process of creating the GUIDs and writing the changes, it was rather slow. Now the process works faster.
 

An additional Progress Panel was added to indicate when the Change Log function gathers the data which will later be written into the Change Log database.

While using MOVE command to move objects with activated Assembly function, we filter out any unnecessary objects.

If there are still issues with performance or crashes, you can use the new checkbox on the Assembly tab of the PlantExpressTools settings.

While using MOVE command check if objectId has links inside database, because DataLinksManager.FindAcPpRowId crashs ACAD if there is no link and doesn't return 0.

This is an issue some customers experienced in some drawing when moving annotations or symbols with annotations.
 

When using the "When saving the Drawing" trigger for the Change Log, the Progress Panel appeared twice.

When using German Plant 3D and clicking on the 'Baumeinstellungen & Zuweisen" node, the following error appeared.

Due to a typo the following dialog can appear:

If geometry parameters use a , (comma) instead of a . (point) it creates an issue. For example: "D1=76,1,D2=..." should be "D1=76.1,D2=...". This lead to the fact, that 1 couldn't be assigned to a dimension name.

In that case, we ignore the wrong parameter "1" and add a warning to PlantExpressTools_Log.txt like:

Please check your geometry definitions for <Plattenschieber ,Wey, MFE, DN65, PN10, FL, A> with SizeRecordId <{78515D85-5565-2851-131B-F043F35C349A}> : "D1=76,1,D2=0.0,L=46,LS=0.0,H11=185,H12=0.0,H21=185,H22=0.0,W1=0.0,W2=0.0,OF=-1.0,B1=0,B2=0.0"

This is a new feature which replaces the out-of-the-box Off-Page Connector functionality of AutoCAD Plant 3D.

Details can be found under: Off-Page Manager

This was more of an oversight.

When deleting Assembly boundaries and using the new mapping feature () we forgot to delete/update the old mapped properties.

When the mapping is updated with the Assembly function, we must also update the annotations, because Plant 3D doesn’t update the annotations itself. Only if the drawing is reopened.

We added a setting in the Settings, Assembly Tab to allow the updating Tags and Annotations.

The Progress Panel which appears when clicking on the Audit button for Assemblies, has a counter now.

The popup History Grid showed history records which aren't needed. This was due to the fact, that changes accepted/rejected through importing changes of the PlantDataManager Plugin lead to these unneeded records.
 

When creating properties with the new assembly settings the list shows Numberic as an available data type. But this should be Numeric. Also using Numberic won't create a double data type in the project database.
 

This message popped up if the polyline which defined the Assembly boundary had a vertex in between the corners of the Polyline. This tripped off the ACAD API.

This was caused by a drawing lock introduced with the new Assembly feature using mapping instead of Acquisitions.
 

During copying of symbols into multiple Assemblies, a symbols was sometimes assigned to multiple Assemblies.
 

There is a new way of using the Assemblies function. Instead of using acquisition rules in Project Setup, the properties of Assemblies can now be mapped.

In addition, the P&ID objects will get the mapped properties of the closest surrounding Assembly. This can be helpful when defining Assemblies which P&ID objects are in scope or not in scope.

This image shows the outer Assembly (PU) and the the inner Assemblies (PU Sub, green and yellow). Everything in green is "In Scope" and everything in yellow is "Not in Scope".

Details are described under Assemblies.

This was implemented together with PT-1090.

It allows the creation of Assembly properties through the PET Settings user interface.

The properties will be created as soon as the Assembly button in the ribbon is used or the Assemblies are updated on drawing save.

The definition of Assemblies was adapted due to the other additions which came with PT-1090 and PT-1185

When the Assembly default symbols are created, we now set the scaling and join type to more useful values.

This change was already included in Version 3.5.0.1245 (10.02.2021)

The Selection List function adapts the path in the UDL file if possible. If the UDL files and the data source (e.g. an MS Access DB, *.accdb) reside in the same folder, the path to the data source in the UDL file doesn't require a path.

The main reason for this adaptation of the UDL files is, that when we will support Vault and BIM360, we do not want:

1.Absolute paths

2.Using [PP] or [PN] in the paths

Here are some examples.

UDL and ACCDB are in the same folder

Before:

Provider=Microsoft.ACE.OLEDB.16.0;Data Source= D:\Projects\Demo Project\PSD Demo XREFs 2018\ACPlantTools\PlantExpressTools\SelectionLists\mw.accdb;Persist Security Info=False

After:

Provider=Microsoft.ACE.OLEDB.16.0;Data Source=mw.accdb;Persist Security Info=False

UDL file in the SelectionLists folder and ACCDB under Related Files

Before:

Provider=Microsoft.ACE.OLEDB.16.0;Data Source=D:\Projects\Demo Project\PSD Demo XREFs 2018\Related Files\mw.accdb;Persist Security Info=False

After:

Provider=Microsoft.ACE.OLEDB.16.0;Data Source=..\..\..\Related Files\mw.accdb;Persist Security Info=False

UDL file using Variables (i.e. [PP] or [PN])

Before:

Provider=Microsoft.ACE.OLEDB.16.0;Data Source=[PP]\Related Files\mw.accdb;Persist Security Info=False

After:

Provider=Microsoft.ACE.OLEDB.16.0;Data Source=..\..\..\Related Files\mw.accdb;Persist Security Info=False
 

When using 'Show Xrefs in Use' from PPM, nothing happened.

When switching between work spaces Plant 3D gets very slow all of a sudden. Also the memory consumption increases. For example when switching between "3D Piping" and "PID ISO" 10 times. In Task Manager you can see "Not responding". Eventually Plant will react and you can close it.

It looks like this:

When using the "Test Connection" button in the "Data Link Properties" dialog from within the PET Selection List Wizard, the dialog searches in the Documents folder instead the folder the file actually resides.

The database will be searched for in the documents folder.

If PCD, PDM Plugin, PET, PL, PS and PSD cannot acquire a network license when Plant 3D starts, the performance became very slow. This was due to the fact, that these PlantTools Plugins checked for a network license multiple times a second.

If no network license was available you get the next two dialogs.

Now these PlantTools check just on startup.

This issue happened if FILEDIA is set to 0 instead of 1. This is now handled.
 

This Bug was fixed due to the fix PT-1010. Previously PET BoltSets or Single Bolt Parts were written into the database before the drawing was saved which isn't correct.
 

This Bug was fixed due to the fix PT-1010 (see next Bug Fix). Now the Isos will not be broken up anymore and connections to Equipment will also be maintained.

When inserting 'Special' valve Dialog #01099 appeared telling the user to restart Plant 3D before creating Isos. In addition, the data in the Properties Palette could show wrong info. For example, a Bolt would appear as a Gasket.

This was due to the fact, that we substituted the original Plant 3D BoltSet with the PlantExpressTools BoltSets or Single Bolt Parts. Now we delete the Plant 3D BoltSet and insert the PlantExpressTools BoltSets/Single Bolt Parts.

The DisplayName for die PET_Fastener sub classes for the Line Number Tag was shown as 'LineNumberTag' instead of 'Line Number Tag' as it is shown in all other standard classes. For whatever reason, the PET_Fastener sub classes didn't inherit the DisplayName from the PET_Fastener class.

We set the DisplayName for all PET_Fastner sub classed individually.

When selecting 3D objects with a combination of standard classes (e.g. gasket, flange) and Bolt Sets/Parts, the Properties Palette shows the 'Line Number Tag' property again.

Properties linked by extended link types in PlantLink are now appearing in PlantExpressTools' Properties Palette.

The Default Values of additional properties for the PET_Fastener class, weren't used/deleted when inserting or updating a flanged connection.

Now the Default Values are used correctly and they won't be deleted.

When the Shop_Field property for the PET_Fastener class was created it was created as a string property not as a selection list.

Now it is created as a selection list and the Default Value is set to "SHOP" like the other Fastener classes.

The issue will also be fixed for existing projects and objects. However, the Default Value will not be set for the existing objects. This has to be done manually. It is the standard behavior of Plant 3D.

After creating a new Isometric drawing, the drawing didn't appear in PlantProjectManager under the corresponding Iso Style. However, in Plant 3D's Project Manager the drawings appeared.

Because we didn't check if the drawings GUID is valid, previously created non-existing isos killed the reading of the remaining iso drawings for the PlantProjectManager tree. Hence, nothing else was shown.
 

If a P&ID drawing is open and then all P&ID drawings are selected for export, all exported have the same content.

Also one of the drawings will be closed and the other stay open, but not the drawing which was open at the beginning.
 

When an Excel file which is used for the PlantExpressTools Selection List function, has rows which have more column with data than the header row used for the configuration for the Selection List function a sort of error appeared.

When clicking OK the next dialog appeared.

No the Excel file will be imported.
 

For P&ID drawings we used the EXPORTTOAUTOCAD command. However, when using XREFs in P&ID drawings, the XREFed drawings didn't bind or xref after the export was done. This was due to to bugs in Plant 3D.

1. According to the Plant 3D documentation the EXPORTTOAUTOCAD command should have the option to handle XREFs. But those options aren't available.
https://help.autodesk.com/view/PLNT3D/2022/ENU/index.html?guid=GUID-86C80CA1-F237-4AE6-8A43-2E9CA06A03A8

2. When a P&ID drawing is exported, you get an error when you try to xref or bind a standard ACAD drawing (e.g. a Title Block) into the exported P&ID drawing.

We now use Insert to bind the XREFed drawings.

We also added a new option to explode the inserted drawings.

'Rule-Based Block Insert' function inserts ALL blocks in the active drawing when ALL drawing which will receive blocks are open.

In other words, If the user opened all drawings which will get blocks and then the 'Rule-Based Block Insert' function is started, ALL blocks will be inserted in the active drawings.

Now the blocks will be inserted in the current drawing if the drawing is already open.
 

When the project category for the project properties uses a space, this space will also be visible in the Setup Configuration file. This prevents the successful setting of the project properties for those categories.

We now use the category and property names and not the display names which may have spaced in them.
 

The dropwown list of previous fitler expressions didn't include the previous expressions.

When entering a filter expression the the PlantSpecDriven palette, the filtering was executed only on the second try.

When opening a drawing with PlantProjectManager, the Plant 3D Project Manager gets opened and stays open.
 

Sometimes an eLockViolation appeared when changing the GraphicalStyle with the PET Properties Palette.

When removing pipe specs from the project in PlantProjectManager...

... only the PSPX file was move to the recycle bin. The PSPC file stayed in the Spec Sheets folder.

When entering PET Settings the following two lines appeared:

Also, if the checkbox to close the Plant 3D Project manager on startup was activated...

The following lines appeared multiple time.

When Change Log was triggered the UNDO command appeared in the command line.
 

Command: Current settings: Auto = Off, Control = None, Combine = Yes, Layer = Yes

Enter an UNDO control option [All/None/One/Combine/Layer] <All>:

Command:

Command: Current settings: Auto = On, Control = All, Combine = Yes, Layer = Yes

Enter the number of operations to undo or [Auto/Control/BEgin/End/Mark/Back] <1>: Enter an UNDO control option [All/None/One/Combine/Layer] <All>:

Now the command is suppressed.
 

Several internal events let the Change Log function write changes into the change log database multiple times. This had the effect, that saving a drawing took sometimes several minutes.

The writing isn't the time consuming part, but before the Change Log can write the changes, it must check what actually changed in comparison to the last saved values.

When AutoCAD's autosave saved the drawing the Change Log was triggered. But in this case it wasn't necessary.

When editing drawing properties with PlantProjectManager with version/revision feature enabled you got an error.

The error looks like this:

We now support AutoCAD Plant 3D 2022.

The new "Project Compare" is included in PlantProjectManager also.
 

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.
 

Up until now only some PlantExpressTools' functions use a license permanently (e.g. SymbolsPalette). Others don't (e.g. Create lists). PlantExpressTools will now use up a license (like PlantSpecDriven and PlantLink) whenever Plant 3D is started.
 

The new Project Compare feature is implemented also in PlantProjectManager.

We updated DevExpress controls and tools to the latest version 20.2.6 in all PlantTools.
 

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.
 

We reorganized the ribbon of PlantExpressTools to get a clearer understanding which functions are more for admins and which ones are for designers.

This is how it looked before:

And this is how it looks now:

In order to have a consistent behavior in all PlantTools tree, the SymbolPalette will not automatically start filtering. Only after pressing the Return key or clicking on the search icon will the auto-filtering be executed.

This is how it looked before:

And this is how it looks now:

When opening PlantProjectSetup and pressing the ESC key, PlantProjectSetup just closed. No matter if changes have been made or not. All changes were lost if the user didn't click on Apply before.
 

PlantTools will run run 14 days in trial period before they stop working.

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.
 

When the project configuration excel file was missing variables which were used in rules an error showed up and prevented the insertion of blocks were the rule was True. Now rules which use variables not used in the project's configuration Excel file are ignored so the other rules will be checked and the function can insert the blocks of the valid rules.

When "Update on drawing save" was enabled, but the current drawing was a P&ID drawing and not a 3D drawing, an error appeared.

When starting Plant 3D and then typing in a filter expression and pressing the Return key in PlantProjectManager, the progress panel showed the loading of the nodes, but then no nodes showed up. Also the filter expression is deleted. When trying again, the filtering works. But it worked with the search icon.

Now it also works when pressing Return.

When drawings were XREFed with an offset and rotation, the offset and rotation was "lost" when binding or keeping the XREFs again at the end of the DWG export process.
 

When auto-filter the tree in PlantProjectManager, Plant 3D crashes when it comes to the node for the Iso.

When changing the status (enable/disable) of any of the checkboxes in the Categories Settings dialog, the OK button didn't get enabled to save the change.

When restoring a value with an acquisition mode...

... we will show a dialog which informs you about the details. If in doubt, click on cancel and change the value manually.

The following grid show all use cases you may encounter. Under result you will see how the Acquisition Mode will change.

There is an additional trigger "When closing & saving the Drawing". This may be helpful, when you do not want to save the changes every time the drawing is save with QSAVE / CTRL+S, but instead only at the end when you close and save the drawing.

If "When closing & saving the Drawing" is disabled but "When saving the Drawing" is enabled the changes will be stored even when closing the drawing and the user clicks on "Yes" when AutoCAD asks whether to save the drawing or not.

When a property already shows a history icon and you change the value, the icon will change to orange. Indicating that there is a new value which hasn't been written into the Change Log.

After you write the changes into the Change Log again, the color will change back to green.

We added the DWG Export settings also in the DWG Export dialog for your convenience.

You will find tabs at the top where you can switch over to the settings.

We added an Overnight Mode. This is interesting for large projects where the export takes several hours. This setting is available only in the Settings tab in the DWG Export dialog. The state of the checkbox won't be stored when closing Plant 3D.

If enabled, any dialogs of the DWG Export function which may appear during the exporting process will be suppressed.

This does not include any Plant 3D dialogs showing up during the export. For example, the message about unsupported locations or missing SHX files. You can suppress those messages yourself so they don't reappear.

We added an icon in-front of the menu item "Restore to this value" in the context menu of the history panel. To see the context menu better.

When you move a drawing to a folder and the folder is also shown in PlantProjectManager, the drawing will also be moved to the folder in PlantProjectManager.

If you moved the file to a different location...

... the file icon shows the broken icon.

After using "Locate Drawing..." the file will now appear under the folder where is physically resides.

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.

When you type in a value in the box above the settings tree, the tree will now be filtered right away while typing in your value.

The "Export to AutoCAD" menu item is reversed if it comes to its enabled/disabled status.

"Export to AutoCAD" must be disabled if the drawing node shows the drawing is closed. And it must be enabled if the drawing is open.

The trigger "When saving the Drawing" was not executed.

When having PID symbols close to the boundary Polyline of an Assembly, the relation ship wasn't always created.

In the image below the left valve didn't become part of the Assembly. Even with using PolyCross in the settings for the Assembly.

The check whether a PID object is within the Assembly or not has been improved now.

When using Overall or Added Length for anything but 100% of the bolts or boltsets X% of the bolts/boltsets was calculated correctly, but the other Y% wasn't.

Out of 12, 6 are correct:

The other 6 bolts show the correct end result, but the calculation method shouldn't show.

Every time the change the column width of the Properties Palette the width will be reset to 50/50 when another object gets selected.

When selecting a new object, the width of the two columns is reset to 50/50.

Now the splitter keeps its position while in Plant 3D.
 

When having a file under related files and then use "Remove File" the following dialog shows:

When clicking on No, the file will be removed anyway. The texts are also wrong, because it says 'drawing' even if the function removes related files.

Now the following dialog appears:

When selecting multiple drawings and trying to increase the version the UI first shows all selected drawings, but when typing in a description all but one disappear. And only this one drawing will then increase.

In addition all drawings showed the same new versions/revision.

As soon as you start typing in the Description, only the first one of the selected drawings will be kept in the dialog.

When no drawing is open and you run "Check for Spec Updates" the following dialog appeared:

Now the function in the context menu is disabled of no 3D drawing is open.
 

When creating a new spec the path was set in the description box which was wrong.

The dialog now looks like this and forces the user to type in a spec and a description before the dialog can be closed.

Removing an empty sub folder doesn't work. The context menu is greyed-out.

Removing an empty sub folder doesn't work. The context menu is greyed-out.

When creating a new project and then using PlantProjectSetup and select either "Bolt Calculation Setup" or "Change Logging" nodes with the Breadcrumb Edit control the following error appears:

Now the control works as Windows file explorer where only the next level is shown.

When trying to insert a P&ID or 3D drawing into a project with "Copy Drawing to Project" an error appeared.

When trying to use "Add Work History" and the drawing is closed, the menu item wasn't greyed-out. Now the menu item is greyed-out if the drawing is closed or opened read-only.

When selecting/changing the "Column Value" for the List Selection an error appeared.

When annotations for PipeLineSegments are set as "Auto-Insert", the "Update Line Annotation" function changed the insertion point of the annotation in case an annotation had to be updated.

When inserting single bolt parts it could happen, that the order index (DwgSubIndex) in the PnPDataLinks table for a connector was either using an index twice or simply used the wrong value.

This was due to the fact, that PnPIDs used in this table could exist for multiple drawings which was something we didn't recognize before.

Now the values in DwgSubIndex is created correctly. Also, the Bolt Update function will fix any existing issues and if there were any the following dialog will appear. It is recommended that you restart Plant 3D in order to see the corrected results on the individual parts of the connector.

When a property is used on multiple tabs in the Properties Palette, the history icon wasn't shown for all properties.

The following pictures show, that the History Icon on the "Pipe" tab (on the right) isn't shown.

When enabling Version/Revision on the Category Settings of PlantProjectManager several functions didn't work anymore (e.g. Creating a new drawing, increasing version/revision).

When the ACPChangeLog database was located on SQL Server and not SQLite the following error appeared:

When a project was using UNC paths it could happen, that an error appeared when entering the Category Settings of PlantProjectSetup. This error disappeared with the Bug fixed PT-781/782 for the MigrationTool.

When using DWG Export the order of binding stacked XREFs becomes important.

If the order is DWG1<--DWG2<--DWG3 (meaning DWG3 is xrefed into DWG2 and DWG2 is xrefed into DWG1, we must bind or insert DWG3 into DWG2 and then DWG2 into DWG1. This wasn't the case so far.
 

It is possible that the column path in the PnPDrawing table doesn't show the correct file name. It looks like Plant 3D doesn't fix this on its own. However, the PnPRelativePath column is updated correctly by Plant 3D.

Therefore, we are now using the file name from the PnPRelativePath column instead the Path column.
 

Sometimes a lock symbol shows on a drawing in PPM after a crash when the drawing wasn't correctly closed.

PlantProjectManager didn't allow opening those locked drawings anymore even if it was by the same user and the same machine.

Trying to restore a value from the history failed.

This bug was introduces with 3.4.0.1000 with the new Change Log feature.

It could happen that the menu item 'Store changes in Change Log' was available in the PlantProjectManager context menu even if the ChangeLoggingSettings.xml file for the Change Log setup didn't exist.

This bug was introduces with 3.4.0.1000 with the new Change Log feature.

Change Logging will store all properties values of a drawing. The storing also includes when an object was inserted, deleted or substituted.

When the changes are supposed to be stored can be defined by triggers.

The changes can later be viewed in the PET/PDM Properties Palette.

In the PET/PDM Properties Palette it looks like this:

The context menu for the Line Group node was not implemented fully.

Before:

Now:

The context menu for the ISO Style node was not implemented fully.

Before:

Now:

The context menu for the Drawing Category node was not implemented fully.

Before:

Now:

The context menu for the Spec Sheet node was not implemented fully. Also, double-clicking on a pipe spec opens Spec Viewer.

Before:

Now:

The MigrationTool is now also part of the PlantExpressTools setup, because it is using the ACProject.db and ACPChangeLog.dcf databases.

There is a new section in the documentation about the MigrationTool.
 

When using F1 in PlantCenter, PlantDataManager, PlantReporter, MigrationTool, PlantCenter or any button in the PlantTools or PlantExpressTools ribbon we open our own browser window.

If a LineGroup is used inside multiple drawings and we run a bolt update or insert a new bolt group into the line we get an exception.
 

When wafer valves were used and the value for the Length property is empty or null, we will try to read the dimension L from the Size Parameters.

All PlantTools write information in log files especially when exceptions appear in the code. You typically see this with error dialogs. When combining the resource files of all PlantTools the log information weren't always written or written in the wrong log file.
 

Somehow we forgot to implement expand and collapse functions in the context menu of the PlantProjectManager tree.

The functions in the menu appear only for what can actually be executed.

Here you see that you cannot collapse, because the tree is already collapsed.

So far,Blind Disk, Orifice Plate, Space Disk and Spectacle Blind were not handled properly. Now we use the parameter H to get the length of the 3D object for the Bolt Calculation.

This issue was resolved with improvements in code.
 

This issue was resolved with improvements in code.
 

Several customer noticed, that using PlantProjectManager with SQL Server projects cause a very slow performance when expanding the tree. This is due to the fact, that the node text in the tree is calculated which takes more time over a network than using SQLite projects.

We changed it in a way, that the node text will be calculated only once now and stored in the PnPDrawing table. Also, the text will be calculated only for the drawings which will be expanded.

If the drawing node text was previously calculated and stored, the text will then be read from the PnPDrawing table which is much much faster.

In case the texts are not reflecting the correct value, you can use the "Refresh AND Recreate" flyout button. Then all previously calculated node texts will be deleted and recalculated.

After you used the "Refresh AND Recreate" feature you should switch back to the green "Refresh". Otherwise the previously calculated and stored node texts will be deleted every time you click on the purple "Refresh AND Recreate" button.
 

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.
 

When two flanged parts use different units the bolt calculations failed. In the Spec Viewer it looks that both parts have the same unit, but in Spec Editor you can clearly see that one is in IN and the other in MM.
 

By default, the order of Fastners for a flanged connection is first the fastener is Gasket and the second the BoltSet.

However, it can happen that the order is reversed which causes problems when we substiture the original BoltSets with the Bolt Parts or BoltSets of the Bolt Calculation function. In this case we patch the DefaultConnectorsConfig.xml so the Bolt Calculation works properly.

To fix existing Bolts it may be necessary to save the drawing and restart Plant 3D after you have updated the Bolts.
 

When typing in a value in a selection list property the PET Properties Palette tried to find a suitable value in the list and if it found one, the selection list lost focus and therefore any additional value was which was typed in wasn't recognized.

In the PET Properties Palette the acquisition mode cannot be changed.

When setting Override mode...

It looks correct...

When the control loses focus it's back to acquire.

When trying to change from override to acquire, nothing is happening at all.

When double-clicking on an object you can enable, that the PET Properties Palette is used instead of the ACAD Properties Palette.

A default value for the number of rows in a drop down list can be defined.

The function creates a GUID you may need to get a unique ID independent of the PnPID.

Resize the Combox Controls (Selection Lists) when needed.

You can now define whether the PET PropertiesPalette is supposed to show only the common properties when selecting different classes, or all properties.

This influences this toggle button.

When using "Show all Properties",

we show multiple lines in the properties palette in case the same property has different DisplayNames.

It looks like PPM tree doesn't allow multi-select anymore, but actually the background color wasn't set properly.
 

When trying to create a version or revision of multiple drawings, only one drawing appeared in the dialog.

When trying to continue anyway, the following error appeared.

Almost all DisplayNames were missing.

When trying to link an annotation which is not created for the PipeLineSegment class or below (here the standard Oval Tag),

The following error appeared.

When using Stub-Ends with lapped flanges,

The StubEnd wasn't added/considered at all in the calculation.

No it is correct again.

The bolt connector symbols sometimes were to short making them "invisible" in a shaded mode. They were visible in a wireframe mode.

The reason was, that we didn't always check which script parameter was the largest one to estimate the required length factor for the bolt connector symbol.

In PlantProjectSetup the folders and drawings for the "Rule-based Blocks" weren't properly ordered.