RealmWorks CSV Import Tool

[Absintheminded78]

Hi Farling,

I'm importing into a new Pathfinder realm. My steps were:

• Create a new Pathfinder Realm
• Add copies of relevant categories (Feats, Magic Items)
• Export that realm's structure
• Create the .rwexport file with your tool
• Import that back into the realm I created

How do I have more than one column appear in a field? e.g. with Feats you have Benefit but also Normal and Special. Is it possible to add more than one column to a field? Or is that part of the initial copying of the category? To add any missing fields before exporting the structure? (I think I know the answer to this already now after thinking about it )
Also, I couldn't see a picture in your post sorry.

Thanks for your help, I'll do another one using the selector now that I know what I'm doing haha.

[Farling]

Originally Posted by Absintheminded78

How do I have more than one column appear in a field? e.g. with Feats you have Benefit but also Normal and Special. Is it possible to add more than one column to a field? Or is that part of the initial copying of the category? To add any missing fields before exporting the structure? (I think I know the answer to this already now after thinking about it )

I think I missed part of this original question.

You can add additional snippets to the category structure within Realm Works before you create the structure-only export. These additional snippets will be available within my tool for you to assign a CSV field to.

e.g. you could create a Labeled_Text snippet and put "Normal" as the label, and then use my tool to populate the message/annotation part of the snippet from a column of the CSV file.

[Absintheminded78]

Originally Posted by Farling

I think I missed part of this original question.

You can add additional snippets to the category structure within Realm Works before you create the structure-only export. These additional snippets will be available within my tool for you to assign a CSV field to.

e.g. you could create a Labeled_Text snippet and put "Normal" as the label, and then use my tool to populate the message/annotation part of the snippet from a column of the CSV file.

Yeah, I managed to get that working Thanks

[Farling]

It is curious because I followed your steps above; except that I imported into a different realm. Maybe it is the re-import into the same realm that is the problem, I will try it out.

At the moment there is only one column per field.

Hopefully you can see the picture as an attachment now.

It is on the TODO to allow the creation of labelled_Text snippets, and also to intermix columns with entered text.

I'm trying to produce an updated version that fixes a slight error when you have both a snippet tag and an annotation in the field. I'm struggling with the installer (the code is already fixed). So in v1.0.0 either set up the tag or the annotation, but not both.

[Absintheminded78]

Thanks Farling, I can now see the picture too. I'll try again and create a new .rwexport file using the tags in the selector.

I'm starting to think that maybe there is an issue with my Realm Works as I had altered EightBitz's spell import script to do the magic items and received the same error about the category not existing but when I checked it in XML Notepad and compared it to my spells import file the structure and content were almost identical (except of course relevant category, tag and facet ID's, it was set to the correct one for Magic Items - category_4).
I'll do some more testing, did you manage to get my file to import ok?

[Farling]

Importing into the same realm won't work at the moment. This is due to me using "Tag_1" as the tag for the new import, but Realm Works has already used this for the export of the structure which was performed.

I tried using a tag id of "MyImportTag" but this caused Realm Works to crash (reported), after reporting about an error during import.

I don't think it's anything that I can fix at my end for the moment.

[davidp]

Originally Posted by Farling

Importing into the same realm won't work at the moment. This is due to me using "Tag_1" as the tag for the new import, but Realm Works has already used this for the export of the structure which was performed.

I tried using a tag id of "MyImportTag" but this caused Realm Works to crash (reported), after reporting about an error during import.

I don't think it's anything that I can fix at my end for the moment.

If you are referring to the tag_id values, they are only used during the import and as long as you don't duplicate them within the import file for different <tag> elements, it should work fine. Even if you are referring to the "name" on the tag in the import file, it should still work fine, although it would be confusing.

As far as the crash, if you haven't done so yet, please open a support ticket, also, so we can track it and contact you directly with more questions.

[Farling]

Originally Posted by davidp

As far as the crash, if you haven't done so yet, please open a support ticket, also, so we can track it and contact you directly with more questions.

Hi David,
I have now raised a support ticket (two actually, one from my old email and one from my new email - Case 119499 and Case 119500).
It is curious that the import works into a new realm just not the original realm.

It all seems related to handling of the import_tag_id.

[ErinRigh]

Does this mean we are limited to one import with your tool?

[Farling]

Originally Posted by ErinRigh

Does this mean we are limited to one import with your tool?

Hello ErinRigh,

No, not at all, the import tool will create one file per category, so you would create one file for each of your different topic/article categories.

Each of these files can then be imported into the same realm.

I have a further tweak to make to the program where you can specify the name of the import (or have it automatically generated), rather than it always being called "Test Import".

The only limitation at the moment, which I've now identified in the first post, is that you can't import into the same realm from which you generated the structure-only export.