Grooper 21.00.0082 is available as of 12-12-2023! Check the Downloads Discussion for the release notes and to get the latest version.
Grooper 23.00.0044 is available as of 06-20-2024! Check the Downloads Discussion for the release notes and to get the latest version.
Grooper 23.1.0026 is available as of 09-16-2024! Check the Downloads Discussion for the release notes and to get the latest version.
Grooper 24.0.0012 is available as of 10-10-2024! Check the Downloads Discussion for the release notes and to get the latest version.
Issue with new batch from CMIS Import
lbellipanni
Posts: 130 ✭✭
I am running Grooper 2.60.0097 and I get the following message when I try to create a new batch from CMIS import
2018-03-12 10:47:30 AM
Import started.
2018-03-12 10:47:30 AM
Executing Query: SELECT loan_no, loan_date, maturity, borrower, document_type, cmis:objectId, cmis:objectTypeId, cmis:name, cmis:contentStreamMimeType, cmis:contentStreamFileName, cmis:contentStreamLength FROM LOAN_DOCUMENTS WHERE (loan_no<>'0')
2018-03-12 10:47:30 AM
An error occurred: Input string was not in a correct format.
at System.Text.StringBuilder.FormatError()
at System.Text.StringBuilder.AppendFormatHelper(IFormatProvider provider, String format, ParamsArray args)
at System.String.FormatHelper(IFormatProvider provider, String format, ParamsArray args)
at System.String.Format(String format, Object[] args)
at Grooper.FieldInstance.SetError(String Message, Object[] Args) in E:\Source\Grooper\v2.61\GrooperLib\Classes\Data Instances\FieldInstance.vb:line 140
at Grooper.DataField.FindInstances(DataInstance Source) in E:\Source\Grooper\v2.61\GrooperLib\Grooper Objects\Data Extraction\DataField.vb:line 915
at Grooper.DataModel.FindInstances(DataInstance Source) in E:\Source\Grooper\v2.61\GrooperLib\Grooper Objects\Data Extraction\DataModel.vb:line 288
at Grooper.BatchFolder.get_IndexData() in E:\Source\Grooper\v2.61\GrooperLib\Grooper Objects\Batch Processing\BatchFolder.vb:line 114
at Grooper.CmisImport.ProcessResult(IObjectData Result) in E:\Source\Grooper\v2.61\GrooperLib\Classes\Import-Export Providers\CmisImport.vb:line 168
at Grooper.CmisImport.RunOperation() in E:\Source\Grooper\v2.61\GrooperLib\Classes\Import-Export Providers\CmisImport.vb:line 67
at Grooper.ImportProvider.StartOperation(Boolean ImportBatch) in E:\Source\Grooper\v2.61\GrooperLib\Classes\Import-Export Providers\ImportProvider.vb:line 149
at Grooper.UI.frmProviderImport.Worker_DoWork(Object sender, DoWorkEventArgs e) in E:\Source\Grooper\v2.61\GrooperUIControls\Forms\frmProviderImport.vb:line 154
Things to note.
I was able to do this on Friday without issue.
I have no issues when I analyze or Execute the query from within the query builder.
Friday I ran with sparse import set to True, but I wanted to go back and set sparse to false to get the actual documents. After failing I set the sparse import flag back to true and still received the error message from above.
Things to note.
I was able to do this on Friday without issue.
I have no issues when I analyze or Execute the query from within the query builder.
Friday I ran with sparse import set to True, but I wanted to go back and set sparse to false to get the actual documents. After failing I set the sparse import flag back to true and still received the error message from above.
0
Best Answer
-
lbellipanni Posts: 130 ✭✭An Update on this. I delete my content models and also deleted the CMIS connections and recreated. Once I did this I was able to import files fine without issue.0
Answers
Product Manager
mharrison@bisok.com