Multiverse: Import Data problem

Mechanics | Upcoming releases | Skeleton

Mockup
Plain

CardName: Import Data problem Cost: R Type: Pow/Tgh: / Rules Text: Import Data has problems importing data directly taken from the exported file in CSV format. Following text is displayed: Flavour Text: Too many non-alphabetic characters in formatting line to deduce CSV separator character. There should only be one, but I found the following: ',','_' Set/Rarity: Multiverse Feedback None

Import Data problem

Import Data has problems importing data directly taken from the exported file in CSV format.

Following text is displayed:

Too many non-alphabetic characters in formatting line to deduce CSV separator character. There should only be one, but I found the following: ',','_'

Updated on 18 Oct 2017 by SecretInfiltrator

History:

2017-09-23 17:27:59: SecretInfiltrator created and commented on the card Import Data problem

by SecretInfiltrator:

Input into Import Data form: Formatting line: "name,code,cost,supertype,cardtype,subtype,rarity,rulestext,flavourtext,power,toughness,artist,art_url,image_url,frame,active"

Character-separated data:""Hottest Gearhunk","RR01","4RR","","Artifact Creature","Golem","rare","Modular 4 (This enters the battlefield with four +1/+1 counters on it. When it dies, you may put its +1/+1 counters on target artifact creature.) Haste (This creature can attack and {t} as soon as it comes under your control.)","","2","0","","","","Red","true""

Response: "Too many non-alphabetic characters in formatting line to deduce CSV separator character. There should only be one, but I found the following: ',','_'"

Issue seems to be: The strings "art_url" and "image_url" are valid field names, but the character '_' is expected to be used as a separator.

Workaround: Use the aliases "art" and "image"

Why it still should be fixed: I feel strongly that the export in CSV format and import in CSV format should be compatible.

by Alex:

D'ohh. I fixed a few problems in Import Data a few months back, but I think I must have introduced this at the same time. Yes, this should certainly be fixed.

Add your comments: