• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

RealmWorks CSV Import Tool

Tool is wonderful, I used it to add a list of spells and it worked perfectly.

I'm looking at adding monsters which has its own layer of problems. I've found some JSON content for monsters here:
https://www.reddit.com/r/dndnext/comments/43a09o/srd_monsters_in_json_format/

JSON works great for storing monsters (multiple actions for example), but terrible as a way to import into realm works.

Any solutions around this that anyone can think of?

Have you tried one of the JSON-to-CSV web converters?

A quick google found https://konklone.io/json/ but it might not like massive files.
 
If you are any good at PF coding in HL pop over to that forum and give me a hand, will ya?

I hate the language - not enough documentation, and too many undocumented macros.

C++ programming is much easier, it's just a shame that I'm UK based rather than US based.
 
Obligatory new member, this is an awesome tool comment. Thanks for this.

I'm glad you like it :-)

If you find you are doing any "work-arounds", then let me know and I'll see if there's a simple improvement to the tool that can help avoid it.
 
I have a source of XML with content I wanted to import. I used my very basic introductory level skills in XSLT to make the CSV to import. My biggest snag was some of the text contained the delimiter (comma). So I enclosed every text field with quotes. But then some of the text also included quotes which messed up the import. For example, the Mind Flayer innate spell charm gives example commands enclosed in double quotes and with comma's. Some web searching quickly found a way for me to add some XSLT to change the double quotes to single quotes which fixed the problem.

So I don't require any changes. However, you did ask about work-arounds, soooo.... an option to delimit by tabs...or something else, might have helped with this.
 
I have a source of XML with content I wanted to import. I used my very basic introductory level skills in XSLT to make the CSV to import. My biggest snag was some of the text contained the delimiter (comma). So I enclosed every text field with quotes. But then some of the text also included quotes which messed up the import. For example, the Mind Flayer innate spell charm gives example commands enclosed in double quotes and with comma's. Some web searching quickly found a way for me to add some XSLT to change the double quotes to single quotes which fixed the problem.

So I don't require any changes. However, you did ask about work-arounds, soooo.... an option to delimit by tabs...or something else, might have helped with this.

Changing delimiter might be possible.

You can go back to double quote by using two double quotes together within the CSV file.

e.g.

Special rate "1.79"

becomes

"Special rate ""1.79"""

(nicked from https://gpdb.docs.pivotal.io/43180/admin_guide/load/topics/g-escaping-in-csv-formatted-files.html)
 
Farling, I noticed that when I import into the realm the new data, each import is displayed as "Test Import".

Is there a way to populate the fields with different information, so the outcome is similar to import from previously exported full/partial realm data?
 

Attachments

  • CSV_Import_result.JPG
    CSV_Import_result.JPG
    58.5 KB · Views: 2
Version 1.22 has just been released.

You can now enter the name of the RW Import.
The name of the generated file will also default to the entered RW Import name.
The installer has been changed to NSIS which is easier to configure than QTIF.

Sorry Valyar, I forgot about this particular annoyance. I should have implemented this a lot earlier in the tool's life.
 
Version 1.22 has just been released.

You can now enter the name of the RW Import.
The name of the generated file will also default to the entered RW Import name.
The installer has been changed to NSIS which is easier to configure than QTIF.

Sorry Valyar, I forgot about this particular annoyance. I should have implemented this a lot earlier in the tool's life.

Without having tried the latest version yet, a suggestion on this matter (might be irrelevant if it is implemented like that already :) ):

  • When RW exports a file, there is meta data about the realm - name, version and etc. The tool reads this data and transfers it to the import file later (can be an option in the GUI or manual inputs for those fields)?

The end result will look like i have exported my own realm to import into it again or something custom.
 
Without having tried the latest version yet, a suggestion on this matter (might be irrelevant if it is implemented like that already :) ):

  • When RW exports a file, there is meta data about the realm - name, version and etc. The tool reads this data and transfers it to the import file later (can be an option in the GUI or manual inputs for those fields)?

The end result will look like i have exported my own realm to import into it again or something custom.

The new text field populates the title of the import, so that is what will appear in the "Imports" window within RW. I have considered adding an additional panel where the other metadata fields can also be set, but that is lower priority than getting the Imports window to show a different name for each import :-)
 
Fabulous :) Looking forward for my next bulk import when time comes!

Until then I am enjoying your RW Output tool... which lately is used quite a lot for player that are reluctant to buy RW.
 
getting this error upon import with the latest version:

The following errors were encountered during import:

Encountered validation error for the import XML: The element 'topic' in namespace 'urn:lonewolfdevel.com:realm-works-export' has invalid child element 'overlay' in namespace 'urn:lonewolfdevel.com:realm-works-export'. List of possible elements expected: 'alias, section' in namespace 'urn:lonewolfdevel.com:realm-works-export'.
 
getting this error upon import with the latest version:

The following errors were encountered during import:

Encountered validation error for the import XML: The element 'topic' in namespace 'urn:lonewolfdevel.com:realm-works-export' has invalid child element 'overlay' in namespace 'urn:lonewolfdevel.com:realm-works-export'. List of possible elements expected: 'alias, section' in namespace 'urn:lonewolfdevel.com:realm-works-export'.

Overlay seems to indicate that an overlay is being imported, but nothing in the tool is supposed to produce this particular element in the import file.

Could you provide a copy of the generated file for me to look at?

If you are familiar with XML, then just the topic containing an "<overlay>" element would be enough.
 
Back
Top