Category to Module, Linked in Category got removed

modules as categoriesredundant categories
3 posts / 0 new
Last post
X 0
Category to Module, Linked in Category got removed

Hi, 

I have been using the category to module feature with mirror new module setting in my model. It works perfectly fine until I removed some category and all category block that has a link into the mirrored modules. The mirrored module got deleted but the link in the category block now only has 1 category left.

There are two case when the above happens:

  1. The link in to these mirrored module have come for a separate module that does not have 'prevent multiple link out setting' turned on (as I need the whole category block to flow to each of the mirrored module).
  2. The link in comes from the same module which has the category to module feature turned on but has the dependant setting in the category block to allow for multiple link out.

 Is there anything that I did wrong in my setup ? 
Any help would be greatly appreciated.

Loom Video demo link : <video link> 

Michael Hutchens A+ 162

Hi Alexander,

Jun is right - there is an option to specify whether or not redundant categories are deleted when deleting modules - it's at the bottom of the Delete Modules dialog, as shown below:

The issue you're experiencing is that this option is always TRUE by default when modules as categories are automatically deleted when categories are deleted, as is the case in your video.

I'm afraid that currently we do not offer this option as a workbook or module-level option, only when deleting modules using the Delete Modules tool as shown above.

As Jun notes, you can always add them back. Another workaround would be to put non-default assumptions within the categories so that they are not deleted, as only categories with default assumptions are determined to be 'redundant' when deleting redundant categories.

Note that this would rarely be an issue in a functional model, as you would/should not have any categories with default assumptions in your model. So once populated with assumptions this should no longer be an issue for you.

Michael