---
title: "Discussion on \"Exporting Pipe Support Parameters That Plant 3D Cannot Export, Live, One Level Below the Data Manager\" | Hashnode"
description: "Discussion on \"Exporting Pipe Support Parameters That Plant 3D Cannot Export, Live, One Level Below the Data Manager\". Pipe support dimensions live in the Python script, not the project database. Read them at run time, write one exportable column, keep it current."
url: "https://hashnode.com/posts/exporting-pipe-support-parameters-that-plant-3d-cannot-export-live-one-level-below-the-data-manager/6ab19bbb022349e083d952aa"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Exporting Pipe Support Parameters That Plant 3D Cannot Export, Live, One Level Below the Data Manager](https://beyond-the-docs.hashnode.dev/exporting-pipe-support-parameters-that-plant-3d-cannot-export-live-one-level-below-the-data-manager?utm_source=hashnode&utm_medium=feed)

Pipe support dimensions live in the Python script, not the project database. Read them at run time, write one exportable column, keep it current.

Sep 21 · 23 min read · beyond-the-docs.hashnode.dev  
Updated Sep 24  
Read the article

-   [#autocad](https://hashnode.com/tag/autocad)
-   [#autocad-api](https://hashnode.com/tag/autocad-api)
-   [#autodesk](https://hashnode.com/tag/autodesk)
-   [#csharp](https://hashnode.com/tag/csharp)
-   [#python](https://hashnode.com/tag/python)
-   [#automation](https://hashnode.com/tag/automation)
-   [#dra-global](https://hashnode.com/tag/dra-global)

## Written by

[Diego Alejandro Peña Esnida](https://hashnode.com/@diegope)

@diegope · Chile

  
[View profile](https://hashnode.com/@diegope)

Self-taught, and stubborn about "impossible".

BIM Development Lead at DRA Global (Chile), self-taught. I build C# .NET plugins for Autodesk products and find things in the Revit API nobody has documented yet. Everything here is measured before it's written; the research is mine, the writing is done with AI. BIM Development Lead en DRA Global (Chile), autodidacta. Construyo plugins en C# .NET para productos de Autodesk y encuentro cosas en la API de Revit que nadie ha documentado. Todo lo que está acá se midió antes de escribirse; la investigación es mía, la redacción la hago con IA.

## Responses 2

Markdown supported · ⌘↵ to post

[Mihai\_LeanZero](https://hashnode.com/@mihaileanzero)

[Sep 21](https://hashnode.com/posts/exporting-pipe-support-parameters-that-plant-3d-cannot-export-live-one-level-below-the-data-manager/6ab19bbb022349e083d952aa/comment/6ab1bae9e30dcf47bdf5ff5f)

The clamp discovery is the best part of this, and it generalizes past Plant 3D. Any tool that validates or bounds input before it draws, executes, or renders it will hand back the typed value through its API, not the applied one, and the two diverge exactly where somebody hit a limit, which is also exactly the case that matters most downstream. Reading the bounds out of the vendor's own script at runtime instead of hardcoding them is the right call for the reason you gave, since scripts get edited and hardcoded copies rot, but it also means the plugin now has an implicit dependency on that file staying regular enough to parse as an if/assignment pair. Did you consider a canary check - re-derive one known support's clamped value from your own read of the limits and compare it against what SupportHelper actually reports, on a schedule, so a vendor patch that reformats the .py breaks loudly instead of silently going back to reporting typed values as if they were real ones?

[Diego Alejandro Peña Esnida](https://hashnode.com/@diegope)

[Oct 16](https://hashnode.com/posts/exporting-pipe-support-parameters-that-plant-3d-cannot-export-live-one-level-below-the-data-manager/6ab19bbb022349e083d952aa/comment/6ab1bae9e30dcf47bdf5ff5f#reply-6ad26f188ac87fa77d405f37)

Mihai, you hit the nail on the head. The implicit dependency on the vendor's coding style (the if/assignment pair) is indeed the fragile link in this chain. If a patch reformats that file, the silent failure mode is catastrophic downstream because the pipeline would confidently trust corrupt data. I hadn't thought about the canary check at all, but your proposal is the missing guard needed to make this completely bulletproof in corporate production. Implementing a scheduled verification against a hardcoded, known baseline model to compare the parsed bounds vs what SupportHelper reports is the exact definition of a clean circuit breaker here. I’m definitely going to bake that canary routine into the orchestrator next week to make it fail loudly if Autodesk alters the script layout. Thanks for the insight—this is exactly the type of architecture review I was hoping for when writing this up. Appreciate the feedback
