JS Script Error IE10

[nvosper]

Hi,

I have an OOTB v8 with all the latest updates, working fine on FireFox and Chrome.

I get errors when trying to use query builder on groups in IE10 though, any ideas? All scripts enabled, trusted sites, etc, etc.

Thanks for the help.

Message: xhrFailed Line: 2 Char: 3100 Code: 0 URI: http://localhost:3333/slxclient/Libraries/dojo/dojo/dojo.js

Nik

[nvosper]

So I've found the error, I debugged the js was calling this -  'c:\\inetpub\\wwwroot\\SlxClient\\jscript\\Sage\\Utility\\nls\\en-gb\\Sql.js', and was 404'ing.

When I actually looked at the folder location 'en-gb' did not exist, however 'en' did, I renamed it and hey presto it worked. Obviously a localisation setting somewhere, I'm now looking into why.

[nvosper]

Obviously I know that this isn't the way to go and we need an en-gb folder in it's own right but I'm curious to know what has caused this and why the folder isn't there or why it doesn't set up as 'en' otherwise?

[AndyShave]

Hi Nick,

I've seen something similar to this, where-by the Query Builder window shows blank screens for the Entity and fields.

I also found that SLX was trying to find the SQL.js script in the en-gb folder.  Again creating this directory fixed the issue, but there is no indication of why this happened in the first place.

I've raised this issue with US support for investigation.

If we identify why this is happening I'll post it on the forum.

Regards,

[mtamborini]

Hi Everybody,

any news on this issue? It looks like when the browser language is set to non english, e.g. de-ch (swiss-german) it's also looking for this folder which does not exist. Creating it manually fixes the behaviour but we can't do this for all possible set browser languages.

[mtamborini]

The Query Builder issue is tracked unter Defect ID 13092451.

[AndyShave]

Hi Nik,

The issue with the Query Builder has now been assigned a defect number.

Defect - 13092482

Currently this defect is being verified by QA and then this has been done Dev can work on a fix.

At that point we should get an idea of which hotfix or version it will be fixed in.

Kind regards,

[nvosper]

Thank you for the update.