SuCri® Knowledge Base 4. Functions of the SuCri modules 4.3. Module 3 (P3D) 4.3.1. Updating all blocks in the active DWG (SuCri3BatchUpdateBlocks)

4.3.1. Updating all blocks in the active DWG (SuCri3BatchUpdateBlocks)

Updated on 20/10/2026

Overview

With Updating all blocks in the active DWG, you bring the block definitions of all SuCri components already placed in the current drawing up to date with the installed manufacturer data. The components of Module 3 consist of AutoCAD blocks. If a manufacturer changes the geometry of a component, you therefore do not have to delete and re-place the existing components; instead, you read in the new block definitions with this command.

Where can I find the function?

Enter the SuCri3BatchUpdateBlocks command in the command line. If Module 3 is pinned to the tool palette, you will find the function there in the Update group under Update blocks.

Plant 3D™ command

Property	Value
Command	SuCri3BatchUpdateBlocks
Tool palette	Module 3 > Update > Update blocks
Keyboard shortcut	No default shortcut
From version	SuCri 25.1.1.1

Video: Updating all blocks in practice

How it works in detail

The command works without any further prompt. In Plant 3D™, SuCri searches the block table of the active drawing for all block definitions whose name starts with g_. These are the blocks of the SuCri components. For each of these blocks, SuCri searches the component models of the installed manufacturer catalogs (folder VendorCatalogues, subfolder PartModels_<AutoCAD-Version>) for a DWG file with the same name without the g_ prefix, for example g_192512 to 192512.dwg. Simplified variants with the suffix _Simplify are read from the same file as the base part.

If a matching file is found, SuCri replaces the block definition in the drawing with the content of this file. Since only the definition is exchanged, all components with this block change at the same time, while the position and assignment of the components are retained. The drawing is then regenerated. The number of updated blocks is shown in the log file (entry blocks updated).

Blocks for which no file exists are skipped. Errors when reading in individual blocks are recorded in the log file, and the command continues with the remaining blocks.

Application examples

Example 1: New manufacturer data installed

After an update of the manufacturer catalogs, the components already placed still correspond to the old geometry. Run SuCri3BatchUpdateBlocks in each affected drawing so that the model and the manufacturer data match again.

Example 2: Renewing only the components, not the connections

If only the component geometries are to be renewed without rebuilding the connections, use this command instead of SuCri3BatchUpdateConnections.

Tips and best practices

Update the manufacturer data first: The command reads the files that are currently installed. Replace the manufacturer data first and reload it with SuCri3ReloadData if necessary.
Affects the entire drawing: In Plant 3D™, all SuCri block definitions of the drawing are processed; a preselection does not limit the scope.
Connections separately: SuCri3BatchUpdateConnections calls this command itself and then also rebuilds the connections.

Troubleshooting

Components do not change: Check whether the manufacturer catalog for your AutoCAD version contains a DWG file with the block name without g_. If it is missing, the block is skipped.
Individual blocks faulty: Open the log file with SuCri3ShowLog. Entries of the form Cannot update Block or Could not find File for Block name the affected block.

Module 3 (P3D), overview of all functions of Module 3 in Plant 3D™.
Troubleshooting Module 3 (P3D), known problems and solutions for Module 3 in Plant 3D™.

Back to the knowledge base