Its a tricky one TBH. When BimorphNodes 2.0 launched I included the Sheets and placed Views as outputs for downstream workflows. However, the output can only exist for a single run as its replaced (disposed) by new sheets output from any subsequent run.
That resulted in 2 workflow problems that lead me to removal these outputs until a better solution can be found (if any, as it would ultimately contravene Dynamo’s graph-update dynamics which disposes all objects with every run):
If the Sheets output was not connected BEFORE running, for say, renaming - like what you need to do - then it couldn’t be used at all since the next run replaced the output with the new set of duplicates
Preventing the node from running, by setting the run input to false as a means of dealing with issue 1 simply nulls all outputs
That said, there may be some decent solutions:
Output the sheets, and if the node’s run input is set to false, continue outputting the same sheets instead of outputting null - essentially, avoid element disposal until run is set to true again. However, this is unlikely to be compatible with Data-Shapes UI since you would need to time a boolean node to switch to false once the duplication process completes
Implement a trace as described here Dynamo ZT Examples - TRACE although this would bring with it its own problems as every run would add to the data store and quickly become unmanageable and not very useful to the user, not to mention the fact that its implementation is far from trivial!
Really, I think solution 1 is best and I will look at the feasibility of implementing this update for BimorphNodes v2.1 expected Q3 2017. In the meantime, you can download BimorphNodes v2.0.2 from the package manager which included the outputs you need.