Improved Check Runs for Part Master Data

In the parts management you now have the possibility to check the part master data directly. To this purpose you can perform the check runs for the part master data in the parts management and the resulting messages are no longer displayed in the message management but directly in the parts management.

In the course of these modifications the project-specific check runs of the previous message class 501 "Part master data" were renamed and moved into the new message class 502 "Part master data". The outdated check run 501019 was removed in the process.

Benefit:

Through the new division of the check runs you can differentiate better between part-specific and project-specific check runs in Eplan. Checking of the part master data directly in the parts management without an opened project is simpler and clearer.

The previously required specification of the scope of the parts to be checked in the part master data navigator is no longer required.

In the parts management you can now also check data of objects that are not available in the part master data navigator, such as supplemental parts.

Performing a check run in the parts management

The new Perform check run popup menu item to execute the check run is available in the tree view and in the tree of the combination view of the parts management. The check run is performed for the selected parts.

After the selection of the popup menu item, the familiar Perform check run dialog is opened. In this dialog you can select a scheme for the check and use the [...] button to branch to the settings dialog for the messages. In the subsequent dialog Settings: Messages and checks you can only carry out settings for the messages from the message class 502 "Part master data" when calling up in the parts management.

New "Messages" tab

The check run results of the check runs for part master data are displayed in the new Messages tab. After performing a check run, a message window with the number of generated check run messages is first shown and the Messages tab is then displayed automatically. To otherwise display this tab, you have to select a main node, such as "Part", in the tree view.

You can jump from a message to the respective part by means of the Go to popup menu item.

Identification and filtering of faulty parts

After a check run in the parts management, parts with faulty or incomplete information are identified in the tree view by a red exclamation mark. To do this at least one check run message has to exist with regard to this part.

In order to have only those parts that were identified as faulty displayed specifically in the tree or list view of the parts management, you can use the renamed property check run Check run messages available as a filter criterion (old designation: Messages in the message management).

Delete check run messages

In the parts management there is a new menu item Delete check run messages under the [Extras] button. After the check run messages for the part master data have been deleted from the parts database by means of this menu item, a message with the number of deleted messages is displayed.

Importing of older projects

The check runs for the part master data were previously saved in the project. If a project is now opened from an older version (2025 and older) and "old" messages for the part master data are still stored in the project, a prompt is displayed - after updating the project databases - whether these messages from part check runs are to be removed from the project.

New check runs for part master data

Two new check runs are available in the message class 502 "Part master data":

The new check run 502042 "The file '<x>' is not located in the master data directory '<z>' foreseen for the property '<y>'" can be used to check whether a file entered at the part is located in the set directory for the respective master data. If this is not the case (because, for example, an image file is not located in the set directory for images), a message is output. Files that are not located in the specified directories cannot be output during the parts data export in the EDZ format.
The new check run 502043 outputs a message when a file is entered for a property at a part for which there is a difference in the upper-/lower-case letters compared to the writing style in the file system. Both the spelling of the file name and the spelling of the file path are checked. Path variables and their contents, on the other hand, are not considered. If, for example, the Eplan\epl-default-cable.jpg file is entered at a part for the Image file property and, in the file system, the file name with the file path is C:\Users\Public\EPLAN\Data\Images\<Company code>\Eplan\EPL-Default-Cable.jpg, a message is output.
Through the standardization of the spelling you can prevent that identical files (images, documents, etc.) are stored several times in an EDZ file due to different upper-/lower-case letters during the data exchange in the EDZ format.