Columns Layout in List View - Does it work?

[Rich Anderson]

I'm going a bit crazy with the list view and columns layout.   What I want is to be able to save different column layouts so I can use them with packages where I have components of the same type, so I can quickly get a list and edit that list "spreadsheet style".   I just can't get this to work reliably and I find my self reconfiguring the layout every time I open the package as a list.   First, I was able to save some different layouts and get them back, but after I added tagged values to one of the layouts, the whole thing just stopped working.  No matter what layout I selected, it just showed me the default which applies to all packages.   Has anyone else had this problem and is there a fix or workaround?    All I really want is to have different column layouts by package.  It seems simple enough, but I have never been able to get this to work reliably.   

[Eve]

It works until you add tagged value columns. When you do, the load fails because the data being loaded is in conflict with the columns currently available.

The workaround is to add all the tagged value columns you need, then save all of your layouts. Hiding (instead of removing) the tagged value columns you don't need.

I've personally been wanting to see this fixed for a while. I believe it has been for 13 (but it may only be fixed for layouts saved in 13.)

[Rich Anderson]

Thanks for that.  I tested it in 13 and it appears to be fixed (but it's still a bit awkward to use)  I can get all the properties and tagged values in the view, but I cannot edit the tagged values 'in line' like you would with a spreadsheet.   For large catalogs (like application inventories, etc.) this would be a good feature and many other EA tools have this.   I'm thinking of writing something that will just exchange data between an Excel spreadsheet and a package  -- not a as an import/export -- but more of a live synchronizer by a 3rd application.