j Jozef
on

 

OpenCDISC Community Edition Validator crashes when validating SDTM datasets in Dataset-XML without (optional) define.xml.

Error message is:

SyntaxError: Unexpected token u at Object.parse (native) at null.<anonymous> (file:///C:/Users/Jozef/AppData/Local/Temp/nw4396_31487/javascripts/application.js:1875:49) at IPCProcess.EventEmitter.emit (events.js:104:17) at IPCProcess.<anonymous> (file:///C:/Users/Jozef/AppData/Local/Temp/nw4396_31487/javascripts/application.js:182:18) at Socket.EventEmitter.emit (events.js:104:17) at readableAddChunk (_stream_readable.js:156:16) at Socket.Readable.push (_stream_readable.js:123:10) at Pipe.onread (net.js:520:20)

Now I recognize that when using Dataset-XML, one needs a define.xml (well, also in the case of SAS-XPT it should, as define.xml is LEADING), but when switching to Dataset-XML, the field "define.xml" should switch to "Mandatory" from "Optional".

When running WITH a define.xml, everything works fine.

When will the source code be available? We do not want to wait for the next release ...

Many thanks in advance,

Jozef

 

Forums: Troubleshooting and Problems

s Sergiy
on January 22, 2015

Hi!

A usage of Dataset-XML files without a define.xml file does not make any sense. It's similar to use a table without column names or any other metadata. Define.xml file is not optional, but required. Sorry for missleading text related to common XPT files only. 

Please be sure that data in Dataset-XML format without a define.xml file is useless.

Kind Regards, 

Sergiy

j Jozef
on January 22, 2015

Thanks Sergiy,

Being one of the developers of Dataset-XML, I realize this very well.

However, the validator should not crash when no define.xml is present. It should giive a message window telling the user that a define.xml needs to be provided. Even better would be that the button "Start validating" is disabled as long as no define.xml is provided (piece of cake to programm that in Java).

Remains my question about the source code. We cannot await a new version of the validator for fixing such and other bugs. And as you know, I always send correted code back to Max and Tim so that it can be used in the next version.

Many thanks,

Jozef

s Sergiy
on January 22, 2015

Thanks for your finding and correct suggestion for expected improvement!

As much I know, our development team are moving to another technology for code repository. It will be published very soon after the next auto-update release with fixed bugs.

Want a demo?

Let’s Talk.

We're eager to share and ready to listen.

Cookie Policy

Pinnacle 21 uses cookies to make our site easier for you to use. By continuing to use this website, you agree to our use of cookies. For more info visit our Privacy Policy.