This year, I found myself doing more complex and/or bulk editing in Excel. I use CSC to create the baseline/foundational CSV file, bulk add a bunch of product, assign dummy channel/cue assignments (this is an existing request to not force this requirement), export to CSV, perform my edits in Excel, and then (re)import the CSV file. Unfortunately, CSC requires the import to be a new show, as opposed to the same show that it originally exported from.

In most situations, this may be OK. Except we had a show setup to use PyroCast which is coded to the original script. Since the client had already publicized the pyrocast code, we were forced to manually replicate all the changes performed in Excel. This was very time consuming.

(Even w/o PyroCast being in play, it would still be nice to be able to import into the same show from which the CSV was created. Perhaps a simple(?) prompt upon import, "Do you want to overwrite this show?" which feels similar to when CSC detects a difference between the cloud and local file.)