English > Support

[FAQ] Aargh.... file path not imported

<< < (2/4) > >>

buah:
Well, as far as I can remember Title and Year columns are must a have. If I'm wrong, sorry to mislead you.

deazo:

--- Quote ---Well, as far as I can remember Title and Year columns are must a have. If I'm wrong, sorry to mislead you.
--- End quote ---
Nostra, could you confirm that please?

When using ID/Path only, PVD seem to recognize the ID's and ask me if I want to update the info for these entries, so I thought it was fine.
I'll test with ID/Title/Year/Path then.

nostra:
ID only should be enough for the case if records already exist in the database, otherwise you need at least one title.

deazo:

 Thanks yes my movies are already there with the right ID's.
 Would you know why the importing does not get the file path by any chance??

rick.ca:

--- Quote ---Would you know why the importing does not get the file path by any chance??
--- End quote ---

Yes. This is what you should be doing...

1. Modify the CSV export template replacing filter="CSV Files|*.csv" with filter="CSV Files|*.txt". The purpose of this is just to create a TXT file so Excel will not open it automatically and instead you can...

2. Start Excel and open the exported file using File - Open (select the "all" or "text" file type). This will invoke the "Text Import Wizard"—which will allow you to specify the delimiter used (i.e., ";") and otherwise ensure the data is parsed properly.

3. Do whatever you need to do to the data (if anything) in Excel.

4. Configure the Excel import plugin by mapping the columns in the sheet to PVD fields. The plugin ignores column headings. Fields must be assigned to each column, in exactly the same order.

5. Run the import plugin. I always forget what the import actions (update, merge, add...) mean exactly, so I remind myself with this post.

Navigation

[0] Message Index

[#] Next page

[*] Previous page