RealmWorks CSV Import Tool

[ErinRigh]

Well now I know what caused it, the Name field and the alias field were the same, I changed it and one other record that was like that and it imported fine

 

[Farling]

Well now I know what caused it, the Name field and the alias field were the same, I changed it and one other record that was like that and it imported fine

Ah, that is good to know. So is it that Realm Works is crashing because the topic name and one of its aliases are exactly the same?

If so, then I can try and put in a check that the topic title and/or any aliases are not the same. It will most likely just report that your import will fail (I think the tool already does this in another situation).

 

[Farling]

Version 2.1 is available

This version contains an additional check when creating aliases.
A warning message is generated if the alias name matches the name of the main topic or another alias for that topic.
The alias is not added to the RWexport file.
(This prevents a crash of Realm Works during import due to an alias name being duplicated.)

This should help ErinRigh avoid similar problems in the future

 

[ErinRigh]

Thanks Farling, like geology, you rock

 

[Happydevil43]

Errors on import

Not sure if I am doing something wrong or what...

I have a csv file that has all the columns in it, I have the associated structure file.
When I do an import with both the suffix, prefix and other name fields, RW gets to either 55 or 85% and crashes or I get the attached message when generating. If I remove the suffix and other name fields I get a successful (somewhat - I need to a heap of post processing) import.

Any ideas ? I am sure it must be me doing something wrong.

I've uploaded the csv file for reference too.

 

[ErinRigh]

Hey, I was just figuring out the same, Happy. Apparently, RW doesn't like it if you have 2 name fields with the same name. For example, I had Thrasher as a name field (surname) and Dale as a suffix (given name) so it would sort it Thrasher (Dale) but then I had Thrasher in the True Name field as well (his callsign) and it crashed the program (RW) when I tried to import so Farling created this version to warn you that it will crash RW

 

[Farling]

Not sure if I am doing something wrong or what...

I have a csv file that has all the columns in it, I have the associated structure file.
When I do an import with both the suffix, prefix and other name fields, RW gets to either 55 or 85% and crashes or I get the attached message when generating. If I remove the suffix and other name fields I get a successful (somewhat - I need to a heap of post processing) import.

Any ideas ? I am sure it must be me doing something wrong.

I've uploaded the csv file for reference too.

Hi Happy,

The warning window is letting you know that the output file has the same named topic more than once. This probably isn't what you intend in your final realm.

This has previously been caused by one or more topic types being created where the parentage that has been set ends up with creating multiple topics.

--

I've just tried with your XLSX and a default structure for pathfinder, and I originally got your error but then realised that I'd started setting up the "adventure area" topic with the name column as well as the "Location" topic type. When I went back to the adventure area and deleted the column name from the name box (right click on the field in the structure panel) the export file was created properly.

(The tool allows you to set up multiple different topic categories for the same output file, so that you don't have to do multiple imports for a single realm.)

 

[Happydevil43]

Thanks guys for your help - baby steps.. .at least I have that problem sorted... so I decided to get adventurous...

I wanted to have an import file that used the storyline topic, but rename the heading and import text.

so I created a new csv file with the headings:
parent, name, prefix, section title 1, section 1 text, section 1 text 2 etc

I then used the storyline topic (I created a copy and added a couple of text snippets)..
The file generated fine, but when I import I got :

Encountered validation error for the import XML: The 'name' attribute is invalid - The value '' is invalid according to its datatype 'urn:lonewolfdevel.com:realm-works-export:name_type' - The actual length is less than the MinLength value.

Attempt to deactivate a record that is still dirty and needs to be saved

I have attached a screenshot of what I did, I am not sure if this is right or not... I am learning my trial and error...

I've posted the same on the RW facebook page too...just in case somebody has advice.

I fully admit that I am playing and learning.....

 

[Farling]

It might be that one of your names is " (a single double-quote character) or it might contain only white space (spaces, tabs, line breaks).

 

[Happydevil43]

It might be that one of your names is " (a single double-quote character) or it might contain only white space (spaces, tabs, line breaks).

found it..... damn nabbit….. was a hidden character that was upsetting it. The only way I could find it was to copy the text from excel into word and turn on hidden stuff....

First test was successful... trying now with a bigger file.

 

[jflevesque]

Duplicate topic in output (import will fail)

Hey everyone,

Really like this tool. I've just begun using it and had great success until today. I am getting "Topic 'topic name' appears in output more than once (the import will fail)." for every entry of my CSV. I've loaded the csv file into Excel, did a sort using the headers and I do not see any duplicate entry in my data (neither in the data table of the tool).

As a test, the name header is the only field I am currently importing, but I am still getting this error. Could anyone take a look and tell me what I'm doing wrong?

I have linked the csv and import structure I am using. Any help would be greatly appreciated!

 

[jflevesque]

Ok, I may have stumbled upon a bug. I restarted the app and it is now working.

 

[Farling]

Ok, I may have stumbled upon a bug. I restarted the app and it is now working.

It might be that you started setting up one topic category and then switched to another topic category.

The tool remembers the settings in both categories, because you might be building an RWexport file that contains more than one type of topic.

You only need to delete the name from the categories which you don't require in order to not generate topics for that category. The name can be deleted by right-clicking on the topic name field to return it to the blank state.

 

[Taronthir]

Question about RW 250 and Importer 2.0

Has anyone else had difficulties with imports with this pairing? I've run into an odd situation where annotations are causing the import to error out. Specifically, it seems the error occurs when placing an annotation on a numeric facet (Label: Numeric field Annotation text box). The numeric field goes in fine, but unless I leave the annotation out of the import, the import hits about 39% and then the application quits with a lovely bug report dialog.

The only other field I've noticed anything strange with is the same annotation on pictures, though that may be unfamiliarity with what data it's expecting, since there was an import error on the report about a name being too short.

 

[Farling]

Has anyone else had difficulties with imports with this pairing? I've run into an odd situation where annotations are causing the import to error out. Specifically, it seems the error occurs when placing an annotation on a numeric facet (Label: Numeric field Annotation text box). The numeric field goes in fine, but unless I leave the annotation out of the import, the import hits about 39% and then the application quits with a lovely bug report dialog.

Hi Taronthir,

Is the text being put into the annotation just good old plain text, or does it contain some HTML markup (or if importing from Excel does it contain some formatting)?

 

[Taronthir]

Hi Taronthir,

Is the text being put into the annotation just good old plain text, or does it contain some HTML markup (or if importing from Excel does it contain some formatting)?

The annotation field should be plain text. Mostly it's just extra notes explaining more about the numeric field - as an example, the numeric field might be the number of attacks per combat turn for an entry, and the annotation might be that the attacks are 2 punches and a head butt. The annotations were all hand-typed, so the only formatting would be whatever excel puts in by default for a general text cell. None of the annotations are larger than about 75 characters, and I avoided both single and double quotes in them. Other special characters might include +, -, or parentheses, but nothing outside of normal punctuation.

I did test this out prior to posting in a test realm - tag and hybrid text annotations work perfectly fine (those are the other two I use in this particular article set), the picture annotate I'm not too concerned about, I included it to be thorough.

 

[Farling]

The annotation field should be plain text. Mostly it's just extra notes explaining more about the numeric field - as an example, the numeric field might be the number of attacks per combat turn for an entry, and the annotation might be that the attacks are 2 punches and a head butt. The annotations were all hand-typed, so the only formatting would be whatever excel puts in by default for a general text cell. None of the annotations are larger than about 75 characters, and I avoided both single and double quotes in them. Other special characters might include +, -, or parentheses, but nothing outside of normal punctuation.

I will have a look at how annotations are managed for each type of snippet at the weekend. Hopefully it is a simple change

 

[Taronthir]

I will have a look at how annotations are managed for each type of snippet at the weekend. Hopefully it is a simple change

Thank you, it would be wonderful if it were. If not, Working around it won't be a huge problem, there are other pieces that I've found I will need to take care of manually - I haven't discovered yet how to make multi-domain tag entries in the csv/xls so they'll be interpreted properly. So I'll do those and the rest at the same time, it's only a minute or so of work for each imported entry.

Regardless, this is a wonderful tool you've created, and with all I've got in the works for importing, it's going to save me weeks or months of typing or copy/paste. Thank you very much for your work and creativity!

 

[Farling]

V2.2 is available

This version will actually create annotations for all snippet types (except labeled text and multi-line snippets). Previously only a few snippet types were supported.

For numeric snippets, the string will be checked to ensure that it contains only digits which are valid in a number. If the field is invalid, an error will be reported in a pop-up window and the generated RWexport file will most likely cause a Realm Works error if you try to import it.

Taronthir, I don't know if this version will help with your problems; but could you give it a try to see if it behaves any differently please.

 

[daplunk]

Messing around a fair bit today with formatting.

This file imports fine but the BOLD text from column W to AN does not work. Interestingly the ITALICs does.

Don't suppose you can poke a hole in why?

File created with THIS.