Closed Re4son closed 2 years ago
Hi,
Unfortunately, the begaviour you describe is not a bug but the way I developped the plugin.
Basically, components can be linked to several models, each of them having their own folders structure. The case you describe with two models only is quite a simple case, but when the database contains dozens or hundreds of models having linked components in different folders, if becomes impossible to know in witch folder to import it.
That's the reason why I import components in their default folder.
I appreciate that behavior when importing selected components but this is not what happens when you import entire models. The entire folder structure is created and:
Yes, you're right. It needs improvement.
I'll work on it and let you know as soon it's done.
You're an absolute legend! Thanks heaps.
My apologies, I do not have a lot of time at the moment. Just to keep you informed, I fixed it when importing elements and still need to fix it when importing relationships.
Would like to add I'm also having this issue atm. Keen for any updates 👍
Hi, I just posted new version 4.9.6 which fixes your issue.
Some components are not imported into the correct folder when the following conditions exist:
These object are imported under the folder "top level folder + 1" and not deeper
Steps to reproduce:
Result: Various object have been moved up from Folder11 to Folder1
Tested with various versions of Archi, various databases, & latest version of db plugin,