> For the complete documentation index, see [llms.txt](https://docs.besmart.software/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.besmart.software/3d-modeling-and-design/smart-connections/update-elements-update-parameters-update-by-dc.md). # Update Elements, Update Parameters, Update by DC

**Update Elements** - will update inserted elements by Instance configuration, by the configuration which was used on selected Host. It will not look into the Configuration saved on computer in Configuration Files Location. **Update Size** - will update only special parameters that have # and ## symbols in front. See more about special parameters in relevant Help page. It will not update location of inserted elements. **Update by Configuration (DC)** - every time Smart Connections is used, the tool will add the shared parameter "DC" to the Host element and write name of configuration that was used:

So if you use **Update by Configuration**, the tool will read the name of the configuration from DC parameter and will find this configuration in Configuration Files Location and reinsert elements by its settings. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.besmart.software/3d-modeling-and-design/smart-connections/update-elements-update-parameters-update-by-dc.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.