Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Folder Tree Structure Preservation on CSV exports/Imports #280

Open
JamesUsmar opened this issue Sep 29, 2017 · 2 comments

Comments

@JamesUsmar
Copy link

Hi,

I was wondering if would be possible to preserve folder structures within the CSV exports and imports?

I create csv files from multiple sources to augment a model, and it would be very handy to be able to automate a folder tree for different "things" (eg locations, devices, nodes etc.) under there respective parent tree entry point.

This is just a management / beautification convenience feature request for elements.csv and relationships.csv files.

As a suggestion you could include a new delimiter field which probably is best to support backward compatibility and any automations out there. Alternatively you could add it to the Type field as a pre-pended piece of text eg "/Machines/Computers/Device" ?

... , Type, ....
... , Device, ....

becomes

.... ,Type , FolderTree , ....
... , Device , /Machines/Computers , ...

Or similar. Thoughts?

Thanks. James.

@Phillipus
Copy link
Member

TBH, I'm more interested in why users are exporting their models into Excel, via CSV, and re-importing them. Would it not be better to have a direct export to Excel?

See http://forum.archimatetool.com/index.php?topic=419.0

@JamesUsmar
Copy link
Author

... ahh not if the data is being "munged" through awk, sed, PowerShell* etc... then parsing CSV is easier.
(*Appreciate XML is well supported with PowerShell)

My ask was just in managing the tree viewer and 1000's of objects in long lists is a little painful. Being able to automate the objects in to convenient containers would be really helpful.

Just a thought.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants