Block name conflicts in command line not working for nested blocks

I have seen the bug fix here: https://mcneel.myjetbrains.com/youtrack/issue/RH-69709 (@dale )
I have been testing this feature and while it works for top level blocks there seem to be a bug still.

Say I have two blocks that each contain two block
Block A:
-Block X
-Block Y

Block B:
-Block X
-Block Z

I insert block A first then block B

1: Any nested block definitions will NOT be redefined. There will be a block called Block X 01

@Dale @mary

I think an ObjectTable.ReplaceInstance is currently done on normal object level.
But I think we need to loop through all objects including IdefObjects?

Could this be?

Being able to import nested blocks using the -insert command while maintaining the block structure for nested blocks would be a game-changer for us. Really hope you can find a solution, @dale @mary ! ! !

Hej Timo -

Following your instructions here, this is what I end up with:

What am I doing wrong?
-wim

Hi Wim.
I made this short video showing the different bewteen using the Insert with pop up windows and the -insert command line option.
With the -Insert it is making a block called “X 01”. As you can se in the video i have the “ResolveConflict” set to “Redefine”
Can you recreate this?

Hi @RasmusWollerStoumann,
I definitely see the issue.
Thank you for the helpful video.
I will get this logged and let you know the YT soon.

Sincerely,
Mary Ann Fugier