We're running Mingle 3.1 and I'm having trouble importing records into Mingle. I'm really just trying to do a bulk update, changing the card type and re-mapping a few other properties (for example, changing 'Criticality' to 'Priority'). I tried importing ~650 records from Excel, but only about 300 went through (they don't even appear in the preview and going Back and then previewing again has no effect). Sometimes, I can break the records into smaller batches and they'll all go through. Many times, however, Mingle will only preview/import the last row. I don't think it's data-specific, because when I copy the n-1st rows from Excel, I still only get one row (the n-1st now).
Have others seen this behavior? Is there a better way to do this kind of bulk update?
Comments
4 comments
Hi Kurt,
I haven't come across this. It's fairly difficult to say what might be going wrong without more information. If you log a support request, they may be able to help.
Good luck,
Jay
Thanks, Jay, I did put in a support request (#5894); I'll post any interesting resolution back here.
Any thoughts on whether my whole approach is reasonable? Should I go through REST? SQL? I don't think I can do bulk property edits because I want to "rename" some properties (such as the Criticality -> Priority, where Criticality does't exist as a property in the new card type and so will be dropped). Certainly round-tripping this in Excel would be easiest for me, but I'm open to suggestions.
Depending on the scope of what you are doing, here are some possible tips.
Those tips are generally the order I would try to do things. First, see if you can make changes with Projet Admin. Then try to use bulk update. Then resort to Excel. That's just me, though. If you're more familiar with Excel than bulk update, preferring Excel instead is reasonable. If those approaches don't work, I would then go with REST.
Using SQL to manipulate Mingle data is a bad idea. It's the quickest way to accidentally get your Mingle database into an unrecoverably bad state.
Thanks for the tips, Jay. I was able to do much of what I wanted in Mingle, but fell back on Excel a few times. I did find that the fewer properties I updated through import, the easier it was. (So long as I had the card number in the row, I was able to update just what I needed.)
By the way, my problem above turned out to be a bug in Mingle (cofirmed with a repro I sent along with the support request). Mingle was choking on the double quote character (") that appeared in the Name filed for several of my records. One character anywhere hosed everything but the last record (which I assume had its own, bug-free, row-handling code).
Please sign in to leave a comment.