Symptoms

Error in loading the form
 

Diagnoses

Hi,

Everyone who are using the application are having this issue. PFB the error details. Please find the attachment for your reference.

There is an error in XML document (1739, 54339).


?Type: SourceCode.SmartObjects.Client.SmartObjectException

?Source: SourceCode.SmartObjects.Client

?Method Base
?Member Type: Method

?Name: GetSmartObjectReader

?Module
?Scope Name: SourceCode.SmartObjects.Client.dll

?Declaring Type
?Full Name: SourceCode.SmartObjects.Client.SmartObjectClientServer

?Stack Trace:
at SourceCode.SmartObjects.Client.SmartObjectClientServer.GetSmartObjectReader(SmartObject smartObject, ExecuteListReaderOptions options, Dictionary`2andamp propertyReference)

at SourceCode.SmartObjects.Client.SmartObjectClientServer.ExecuteListReader(SmartObject smartObject, ExecuteListReaderOptions options)

at SourceCode.Forms.AppFramework.FormsApiToXml.ToXmlList()

at SourceCode.Forms.AppFramework.FormRuntime.SmartObjectExecution(XPathNavigator nav, Boolean outputDependencies, SmartObjectClientServer svr)

at SourceCode.Forms.AppFramework.FormRuntime.WorkXmlToApi(String xml)

at SourceCode.Forms.Runtime.AJAXCall.ProcessRequest(HttpContext context)

Thanks,
Kishore.
 

Resolution

Dear Kishore,

Following our meeting yesterday,

We?ve been able to track, and solve the issue related with case reference ?F02_001559? of the List for SharePoint.
It seems that a ?Non-Ascii? character (CHAR(16), ',--!DLE]') )had been added using copy / paste from another source who occurred this error.

I tested the import of your list template in a SharePoint Environment using a version 2013 and the 4.7 of BlackPearl after the test made by Olivier on a SharePoint 2010, and we?ve been able to track and see that the character ?Non-Ascii? was present on the Sharepoint table.
The good fact is that with the 4.7 we are able to execute the ?SmartObject? without any error ( But Only with the configuration ?Sharepoint 2013 + Blackpearl?).

The environment ?BlackPearl 4.7 + SharePoint 2010? was not tested and we don?t know if it work or not.

My colleague Olivier Chatagnon has created a script yesterday that he will share with you in order to track for a distant future any bad character that I attached on the ticket.
At the end of the execution of the script you need to take the copy of a statement reflected by the creation of a specific SQL procedure ?dbo.ShowWhiteSpaceK2FranceCheck?.
Paste the query and you will able to retrieve the rows impacted by the ?Non-Ascii? character.


Thank you and best regards,
Nasser SAID

K2 | TECHNICAL SUPPORT ENGINEER