Regarding Galaxy dump / CSV files from IDE

Hi Jacob, as long as you have the 'Only Update changed attributes' option upon import, then its enough to include only the updated columns in the import file (And Tagname of course).

Renaming object instances, or Attributes is not possible in this way. (you can import the new updated instance names and afterwards delete the old instances though).

But if you rename the Attribute in the csv file, import the instance using replace option, then it will recreate the instance with the new name, then all content needs to exist in the csv file though.

Other more advanced bulk manipulations of templates or instances, I would use GRAccess.

Hi Jacob, as long as you have the 'Only Update changed attributes' option upon import, then its enough to include only the updated columns in the import file (And Tagname of course).

Renaming object instances, or Attributes is not possible in this way. (you can import the new updated instance names and afterwards delete the old instances though).

But if you rename the Attribute in the csv file, import the instance using replace option, then it will recreate the instance with the new name, then all content needs to exist in the csv file though.

Other more advanced bulk manipulations of templates or instances, I would use GRAccess.

In addition to working with Attributes on an instance it can become more complex, attributes involve more than one column, the column "UDAs(MxBigString)" and the Attribute specific columns.

and the UDAs colums must contain all attributes on the object, here it is not possible to specify only the updated ones. 

Thank you!