• Not Answered

Does anyone know of a way to bulk edit the "Ignore" flag for module blocks in class-based modules?

Does anyone know of a way to bulk edit the "Ignore" flag for module blocks in class-based modules?

The only exposed parameter in the "create format file" wizard is ".MNAME" as follows: MODULE_BLOCK_BINDING.MNAME.

This parameter will contain a module name when assigned, but if it does not contain a module name it may be unbound or ignored.

Here is what the two states look like in Explorer. Notice that when you select "Ignore", it shows "<IGNORED>" in the the bound module name field, though I can't seem to access that info.

Inside the FHX this is what the empty module block looks like in the two states (unbound versus ignored)
MODULE_BLOCK_RESOLUTION NAME="BLOCK10"
{
MODULE=""
IGNORE=T
}
MODULE_BLOCK_RESOLUTION NAME="BLOCK11"
{
MODULE=""
IGNORE=F
}

I tried various manual format file edits to no avail.

I selected the IGNORE flag for the module blocks in my template, but when I bulk build a module using the template, leaving MNAME blank in the import file, the import succeeds but all of the blanks change from <ignored> to <unbound>.

So long story short: does anyone know of a way to bulk build (or bulk edit) modules that contain module blocks in such a way that they come out the other end with the "Ignore" option selected? Note: I am using shared ownership as opposed to private in this case and my module template is class-based.

Thank you for any ideas, knowledge, or suggestions that you can share.
Thanks in advance!

P.S. I think it is greate that @ Andre D. and Matt S. are built in Tags in this forum haha. 

• bulk editing
• module block
• IGNORE
• unbound

Dave Grubwieser

• 12 Dec 2025 12:31 AM
• Cancel

3 Replies

• dgrubwieser

  

  • 4 Feb 2026 11:00 PM

  Bump. In case anyone may have an answer? Thank you.

  • Cancel
• gamella

  

  • 5 Feb 2026 11:51 AM

  Unfortunatelly is not possible just using bulk edit.
  Even if module blocks are IGNORED in the module template, a module created using that module template is generated with devices unbound instead of ignored.

  • Cancel
• dgrubwieser

  

  • 6 Feb 2026 2:30 AM

  In reply to gamella:

  thank you for the reply.
  
  Today I also broke one from class and then re-classed it. When you do that: all unbound and ignored module blocks create a module of the underlying class type used, and when you re-class, you have to manually ignore everything all over again.
  
  It's still a helpful construct to design class-based equipment modules for consistency/repeatability, but unfortunately this one annoying manual step can't be avoided. Could be one for the "Submit your Ideas" forum.

  • Cancel