RealmWorks CSV Import Tool - Page 51

Farling · 07:37 AM

Version 2.7 is available

User can now choose which sheet inside an Excel document to be used as the data source. Note that only one sheet from an Excel document can be used in each project (as requested by Janrith in http://forums.wolflair.com/showpost....&postcount=487).

Provide warning about unsaved work when attempting to load a new project, load a new data file, load a new structure file, or choosing a different worksheet in the current excel data set (as reported by Janrith in http://forums.wolflair.com/showpost....&postcount=517).

Ensure that the data mappings are shown when loading a project. (This was just a display bug, the mappings were known behind the scenes.)

jflevesque · November 3rd, 2019, 05:53 PM

Hey guys and gals,

I have just finished cleaning up a csv file for import for my ToA game (creatures only), and I am getting a validation error during import:

Encountered validation error for the import XML: The 'format_version' attribute is invalid - The value '4' is invalid according to its datatype 'urn:lonewolfdevel.com:realm-works-export:version_type' - The MaxInclusive constraint failed.

I did a quick search of the forums and didn't find anything pertaining to this. Also, it seems to completely block the import process. I am using v2.7 of the import tool, in case it is related to the tool.

Did any of you ever encounter this? Any fix or workaround?

Farling · November 3rd, 2019, 11:06 PM

Quote:

Originally Posted by jflevesque

Hey guys and gals,

I have just finished cleaning up a csv file for import for my ToA game (creatures only), and I am getting a validation error during import:

Encountered validation error for the import XML: The 'format_version' attribute is invalid - The value '4' is invalid according to its datatype 'urn:lonewolfdevel.com:realm-works-export:version_type' - The MaxInclusive constraint failed.

I did a quick search of the forums and didn't find anything pertaining to this. Also, it seems to completely block the import process. I am using v2.7 of the import tool, in case it is related to the tool.

Did any of you ever encounter this? Any fix or workaround?

I noticed with the latest version of RW that was released that the version number of the file got increased.

I haven't yet done an analysis to see what might have changed in the format of the structure/data parts of the file.

I will get a look over the coming week and see if I can ensure that imports will start working again.

The_Traveller · November 4th, 2019, 01:53 AM

I noticed this too. I went in to my structure file and changed the XML type to 3 and that fixed the problem going forward. If you already have a conversion done, you can go into that file and make the same change and yte import will work just fine.

jflevesque · November 4th, 2019, 04:09 AM

Hi The_Traveller, I just tried your suggestion and that worked! My guess is that LoneWolf forgot to update the validation code in the import function to take into account the new structure version. I haven't tried yet, but my guess is that full realm exports don't work anymore

Farling · November 4th, 2019, 11:22 AM

Quote:

Originally Posted by jflevesque

Hi The_Traveller, I just tried your suggestion and that worked! My guess is that LoneWolf forgot to update the validation code in the import function to take into account the new structure version. I haven't tried yet, but my guess is that full realm exports don't work anymore

No, it is more likely that the Import tool is missing some new data which is required for version 4 of their XML format.

Acenoid · November 4th, 2019, 09:53 AM

What did they change in the structure exactly that would not make it work anymore?

Farling · November 4th, 2019, 11:02 AM

Quote:

Originally Posted by Acenoid

What did they change in the structure exactly that would not make it work anymore?

It looks like there is a new attribute which is mandatory somewhere.

Acenoid · November 6th, 2019, 02:38 PM

So, but if we just update the version umber it still seems to work right? (Ok, who knows what consequences this would have... maybe I should try this on a fresh realm)...

Your import tool is really great, it would be very disappointing if it can no longer be properly used, just because the most recent update of RW (and presumedly the final one for the foreseeable future) was not done tested properly...

Farling · November 9th, 2019, 01:03 AM

Version 2.8 is available

This version has a new entry in the Options menu.
When selected, it will force the format_version attribute in the generated XML file to be set to 3.

This is a work-around for what appears to be a bug in Realm Works version 254 whereby it would generate export files with a format_version of 4, but can only read import files with a format_version of 3 or earlier.

The option is NOT selected by default.

Existing saved projects should still load, and when you next save the project the current state of the new menu option will be saved as part of that project.

The_Traveller Member Join Date: Nov 2017 Posts: 32 November 4th, 2019, 01:53 AM	I noticed this too. I went in to my structure file and changed the XML type to 3 and that fixed the problem going forward. If you already have a conversion done, you can go into that file and make the same change and yte import will work just fine.
#4

jflevesque Member Join Date: Jul 2016 Posts: 55 November 4th, 2019, 04:09 AM	Hi The_Traveller, I just tried your suggestion and that worked! My guess is that LoneWolf forgot to update the validation code in the import function to take into account the new structure version. I haven't tried yet, but my guess is that full realm exports don't work anymore
#5

Acenoid Senior Member Join Date: Dec 2013 Posts: 798 November 4th, 2019, 09:53 AM	What did they change in the structure exactly that would not make it work anymore? Join the (unofficial) Realm-Works IRC Chat: #realm-works on the Rizon Network (https://wiki.rizon.net/index.php?title=Servers) -> Browser Client: https://kiwiirc.com/client/irc.rizon.net
#7