cancel
Showing results for 
Search instead for 
Did you mean: 
EN
cancel
Showing results for 
Search instead for 
Did you mean: 

More Control Over Nested Modules in Module Linking

lorianerfreire
Contributor

Short Summary:

Please allow selective inclusion of nested modules when linking hotlinks.

Currently, we can only include all or skip all nested modules, which leads to duplication issues in multi-file workflows.

In these situations, modules are often kept as .pln files instead of .mod due to documentation needs, which further complicates coordination. The ability to choose exactly which nested modules to include (e.g., include module E but exclude module B) would greatly improve control and workflow efficiency.

Description:

I would like to suggest an improvement regarding module linking and nested modules in Archicad.

 

Currently, when linking a module, we can choose whether to include or exclude its nested modules as a whole. However, there is no option to selectively control which nested modules are included.

 

I am aware that there is already a similar request regarding nested hotlinks, but I found it somewhat unclear and broad. For that reason, I wanted to describe this specific need in a more objective and practical way. (https://community.graphisoft.com/t5/Wishlist/Nest-Module-Exclusion-Options/idi-p/690669)

 

In complex project structures, this becomes limiting. For example:

  • File A (main/master file)
  • File B (site/terrain)
  • Files C and D (buildings)
  • File E (typical floor module)

Setup:

  • File A contains modules B, C, and D
  • Files C and D contain module E
  • Additionally, files C and D also require module B (site)

As a result:

  • File A ends up containing B directly, and also indirectly through C and D
  • This creates duplication of module B (in A, C, and D)

 

Even if B is only placed in either C or D (instead of both), duplication still occurs once everything is brought into file A.

 

The current workaround is to disable nested modules, but this is not viable because module E (the typical floor) still needs to be included.

 

Additionally, in many of these workflows, modules are maintained as .pln files instead of .mod files due to documentation requirements. This makes the issue even more relevant, as coordination becomes more complex and the limitations of nested module control are more evident.

 

Request:

It would be extremely useful to have more granular control when placing modules, specifically:

  • The ability to choose which nested modules to include or exclude individually
  • For example, when placing modules C and D into file A, I would like to include module E but exclude module B

 

This feature would significantly improve workflow flexibility and help avoid duplication and coordination issues in multi-file projects.

This feature would significantly improve workflow flexibility and help avoid duplication and coordination issues in multi-file projects.

Status
Open

with 0/200 Votes 0%