database-plugin icon indicating copy to clipboard operation
database-plugin copied to clipboard

Nested folders not recognised when importing certain components from db

Open Re4son opened this issue 2 years ago • 6 comments

Some components are not imported into the correct folder when the following conditions exist:

  • Folder structure is deeper than top level folder + 1
  • Importing components from db into model imported from db
  • Certain objects only, e.g. Value Stream, Application Component, Data Object, Constraint, etc.

These object are imported under the folder "top level folder + 1" and not deeper

Steps to reproduce:

  1. Create new model and export to database
  2. Export attached example model containing nested folder structure into database
  3. Close all models in archi
  4. Import new model from step 1
  5. Import components from db into model and choose the model from step 2

Result: Various object have been moved up from Folder11 to Folder1

Tested with various versions of Archi, various databases, & latest version of db plugin,

Re4son avatar Jul 28 '22 05:07 Re4son

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.

herve91 avatar Jul 28 '22 11:07 herve91

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:

  • some of the objects are placed in the correct folders
  • some are place one folder beneath the default folder
  • none are place in the default folder

Re4son avatar Jul 28 '22 21:07 Re4son

Yes, you're right. It needs improvement.

I'll work on it and let you know as soon it's done.

herve91 avatar Jul 28 '22 21:07 herve91

You're an absolute legend! Thanks heaps.

Re4son avatar Jul 28 '22 22:07 Re4son

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.

herve91 avatar Sep 07 '22 09:09 herve91

Would like to add I'm also having this issue atm. Keen for any updates 👍

Ellers01 avatar Oct 06 '22 00:10 Ellers01

Hi, I just posted new version 4.9.6 which fixes your issue.

herve91 avatar Oct 26 '22 01:10 herve91