The Essential Project Forum

Hi,

I'm trying to import external repository data into EAM.

So I created a XLS source file according to EMM constraints, populated it with data from external repository and ran the import with Import Utility. It executed without any problem on test environment, and on live environment too.

Then I generated a DUP import file to integrate new data into EAM, using the Essential Update Tab in Protégé. At this step, the tab only prints the following message: The console window prints the following error stack:
Does anyone have already encountered this error ?

Data spreadsheet and import spec are attached to this post for more details.

Thanks for any help.
Regards

Hi,

Maybe I'd better have to run Import Utility against a Protégé server than a local Protégé, as described here, so IU would write directly into EAM, but I'd be glad to understand what's the problem with tue DUP file use in a local dev environment.

Thanks for any advice.

Hi,

From the error message that you are seeing, I think you have some 'invalid' characters in the source data that you are importing. The usual suspects to look for in your source data are "smart" quotes and similar non-standard characters, typically from MS Excel

Jonathan

Hi Jonathan,

Thanks for your reply. I saw the UTF-8 error in the message, but the problem occurs even with only the following data, without any non-standard characters :

• Tech_Comp name : Annuaire
• Tech_Comp realisation_of_technology_capability : Identification

Here are the test files (xslx, spec, script) and the DUP file.

Regards,
Gunther

Hi Gunther,

Thanks for posting back.

I’ve had a look at your test files with the following results:

When I unzipped your ‘test_import_270218_134039.zip’ and renamed the resulting ZIP as a DUP, I replicated the error that you report.

However, when I created a new Import Activity in my Import Utility, using the exported specification you supplied it ran successfully with your supplied spreadsheet. I then used the ‘Generate Import File’ button in step “4. Execute Import Utility” to get a ‘DUP’ file.

When I ran this using the Essential Update Tab it ran successfully, creating the new Instances as expected.

How did you create the DUP file that you included? It seems to be malformed in some way

Thanks

Jonathan

Hi Jonathan,

I generated the DUP file from Import Utility 1.7.2 on step "4. Execute Import" using the "Generate Import File" button as you did.

I'm running Import Utility locally on Windows 7.

I'd be glad to use the DUP import with Essential Update Tab, as it would make me save a lot of time, but I don't see what could be the problem...

Regards,
Gunther

Thanks very much for getting back to me Gunter,

The issue is that one of the files in the generated DUP has invalid XML character, which is a bug in the Import Utility.

I have made a fix to the Import Utility and tested this with characters such as the é in your Import Activity description and it works now.

This fix will be in the next release of the Import Utility.

Until then, if you update your Import Specification description to change Activité to Activite and re-generate your DUP, it should then import successfully.

Jonathan

Many thanks Jonathan!
I'll wait for the patch release. I'll test the REST API too.
Regards,
Gunther