If you have access to the source code (RDA – Report Design Aid) or the SQL query behind JTB BatchAttEdit, implement the following changes immediately.
We all know FIND (Ctrl+F) in AutoCAD, but it can be risky—sometimes it replaces text inside dimensions or leaders when you only meant to edit block attributes.
How to make it better: JTB BatchAttEdit has a built-in Find and Replace function that is strictly limited to block attributes.
If you work with AutoCAD and utilize dynamic blocks with attributes, you know the pain of the Block Editor. Clicking into a block, changing a value, closing the editor, and repeating that process 50 times is a surefire way to ruin a perfectly good afternoon. jtb batchattedit better
For years, the standard solution was the BATTMAN (Block Attribute Manager) or the EATTEDIT commands. But let’s be honest: they can be clunky, slow, and prone to user error.
Enter JTB BatchAttEdit. It has become the go-to tool for professionals who need to process data quickly. But are you using it to its full potential?
In this post, we explore how to make your workflow "better" by mastering the hidden efficiencies of JTB BatchAttEdit. If you have access to the source code
For power users, making jtb batchattedit better means going beyond the GUI. JTB BatchAttrEdit supports scripting via VBScript and JavaScript expressions in attribute values.
Example: Automatically set a LAST_EDITED_BY variable to the current Windows user.
In the “New value” field, enter:
= GetUserName()
Example: Increment a drawing revision based on the current revision letter.
= Chr(Asc([REVISION]) + 1)
(This changes “A” to “B”, “B” to “C”, etc.)
Even better: Combine scripts with PDM events. Use BatchAttrEdit’s command-line mode as a post-check-in workflow trigger. When an engineer checks in a file, the system automatically updates the DATE_RELEASED variable on all referenced children. Example: Increment a drawing revision based on the