Lattenkiste 4 years{"ops":[{"insert":"I have my collection on MTGCollectionBuilder and want to import them into Archidekt so I can build decks with them, but the imports are full of errors.\nI've attached screenshots of the export options and what the export csv looks like, which doesn't really match Archidekt import example, and also a screenshot of all the errors.\n\n\n"},{"insert":{"image":"http://lattenkiste.com/wp-content/uploads/2020/10/MTG-export.png"}},{"insert":"\n\n"},{"insert":{"image":"http://lattenkiste.com/wp-content/uploads/2020/10/import-errors.png"}},{"insert":"\n"}]}
0
Jeremy(Archidekt Moderator)
4 years{"ops":[{"insert":"So what I'm seeing is that all of the import errors are for cards that imported with parentheticals in their name \"columns\". Since the importer only recognizes card names, this is confusing it. The basic lands, for instance, should have the collector numbers that specify exactly which land art it is in a separate column for collector number. Similarly, to specify that you want a certain Boros Guildgate art or the showcase version of Daxos, Blessed by the Sun, including the specific version's collector number in a separate column and stripping the parenthetical in the card name column will get you there. \n\nI understand that since this is the file you got from MTGCollectionBuilder, these weren't conscious choices made on your part. My best suggestion for an immediate fix is to ctrl+f all parenthesis in your CSV file and delete them. If you care about what those parenthesis were specifying (though it looks like they were just inserting them for you as the cheapest option), you can put the numbers in another \"column\" (separated in the CSV file by commas) and tell our importer that it should read those numbers as collector numbers. \n\nIf we see this cropping up too much, we may end up needing to change our importer to ignore parentheticals, but hopefully this helps you a bit in the meantime. I apologize for the frustration! \n"}]}
0