Concept: An automation tool for SAP2000 that eliminates manual data filtering. It instantly extracts and groups end-forces (Start/End) of selected frame elements based on their section profiles. Key Features: Automatic Selection Sensing: Analyzes only the elements currently selected in the SAP2000 model. Station Filtering: Focuses strictly on s=0 and s=L stations to capture critical design forces (N, V, M). Profile-Based Categorization: Automatically groups results by section types (e.g., IPE, HEB, SHS) for cleaner data management. One-Click Export: Streams structured data directly to a table or Excel, bypassing the heavy "Display Tables" menu.

Hey everyone, Let's talk about one of the most frustrating limitations in Tekla: transferring drawing files between completely different models. We all know that .dg files are strictly tied to the 3D model's internal database and part GUIDs. If you have two separate models (maybe a heavily modified revision, a split phase, or you're just trying to salvage drawings from a corrupted model), you can't just copy the drawing files over. Cloning works to an extent, but it requires the 3D geometry and numbering to play nice. The Idea: What if we built an API tool that "strips" the raw 2D drafting data from a drawing? I’m talking about extracting the manual dimensions, text marks, view boundary coordinates, and manual linework, and exporting them into a lightweight format like JSON or XML. Then, in the new model, the "Injector" part of the plugin reads that data and recreates those 2D elements onto a new drawing view. It essentially temporarily decouples the intelligent 2D edits from the 3D database, allowing you to paste your hard-earned drafting work onto similar parts in a new model, or at least bring it in as "dummy" 2D linework/text to save hours of detailing. Has anyone ever tried to bypass the GUID system like this using the Tekla Open API, or tried parsing the raw data inside .dg files? Is this a pipe dream, or actually doable? Let me know your thoughts!