Jump to content

Export Sets - Exception starting job: Conversion from type 'DBNull' to type 'String' is not valid


Cody Luera
 Share

Recommended Posts

  • IPRO Employee

This error occurs when the 'EndDoc' system field is not populated for the documents included within your Export Set search. The error will only occur if you are using the option to select an Image Priority for the Export Set.

 

To resolve this error, the EndDoc field will have to be populated with data for the documents that are being exported.

 

If you do not have the values, you can populate the EndDoc with the BegDoc. This can be done by editing the search that is being used for the Export Set, then adding the following search parameter: EndDoc Not Set (see image).

capture.jpg.c610970a64887807c5b4de77985eae3d.jpg

 

This will return any documents that DO NOT have the EndDoc field populated. Then, ensure that the BegDoc and EndDoc values are added to the grid display, and use the Mass Action -> Export feature to save a CSV file of the BegDoc and EndDoc values.

 

Next, edit the CSV with an editor program such as Excel. Again, make sure to remove any extra columns, so that only BegDoc and EndDoc are left. Copy & paste the BegDoc values into the EndDoc column. Save the CSV, then proceed to import it via Eclipse Admin -> Import Data. On Step 2. Map fields, be sure to map the BegDoc and EndDoc fields to the correct case fields. For the import method, please select 'Overlay Only'. This will import the BegDoc values as the EndDoc.

 

Once the EndDoc is populated, you can then run the production again, and this will prevent the error from occurring.

Edited by Cody Luera
  • Like 1
Link to comment
Share on other sites

Thanks Cody for the workaround, but would like to know the reason behind this requirement to have enddoc populated. This is not required in earlier versions. We have several old cases which do not have enddocs populated. It is waste of time. And if this is such big requirement than it should be part of the validation process and not an after export check.

Link to comment
Share on other sites

Vaibhav,

 

The production staging database requires an enddoc to be populated. This is due to a logic change on how productions are handled when using image priority.

 

When creating new numbers during a production, this is generated automatically. When using image priority and attempting to use the original image of a document, then that document would require an enddoc so that the production database can be populated with a production enddoc during the staging of the production. The production enddoc is used to determine whether or not the suffix should be used when creating the production image key.

 

If you are using image priority and selecting a production and limiting the selection to only previous productions, then an enddoc should not be required for a document in production set.

 

There should be changes made to the validation process in Eclipse 2016.3.1.

 

Thank you,

Levi Roble

Technical Support Engineer 2

Link to comment
Share on other sites

  • 2 weeks later...
  • IPRO Employee
This error occurs when the 'EndDoc' system field is not populated for the documents included within your Export Set search. The error will only occur if you are using the option to select an Image Priority for the Export Set.

 

To resolve this error, the EndDoc field will have to be populated with data for the documents that are being exported.

 

If you do not have the values, you can populate the EndDoc with the BegDoc. This can be done by editing the search that is being used for the Export Set, then adding the following search parameter: EndDoc Not Set (see image).

[ATTACH=CONFIG]n1103[/ATTACH]

 

This will return any documents that DO NOT have the EndDoc field populated. Then, ensure that the BegDoc and EndDoc values are added to the grid display, and use the Mass Action -> Export feature to save a CSV file of the BegDoc and EndDoc values.

 

Next, edit the CSV with an editor program such as Excel. Again, make sure to remove any extra columns, so that only BegDoc and EndDoc are left. Copy & paste the BegDoc values into the EndDoc column. Save the CSV, then proceed to import it via Eclipse Admin -> Import Data. On Step 2. Map fields, be sure to map the BegDoc and EndDoc fields to the correct case fields. For the import method, please select 'Overlay Only'. This will import the BegDoc values as the EndDoc.

 

Once the EndDoc is populated, you can then run the production again, and this will prevent the error from occurring.

 

Re-posting the screenshot for better clarity.

13b96b38251fb71cb622024b104196ee.jpg.bbf36c297cd4b4b51b0c898095141dd8.jpg

Link to comment
Share on other sites

  • 6 months later...
  • Cloud Solutions Architect

If you need to populate ENDDOC for your documents that have images, you can identify and create an overlay file using SQL that will list the last suffixed imagekey for the documents in question. You can use this script:

 

Select D.DocumentKey AS BEGDOC, MAX (ImageKey) AS ENDDOC

from Documents D

join Documentpages P on D.DocID = P.DocID

group by P.DocID, D.DocumentKey

ORDER BY D.DocumentKey ASC

Link to comment
Share on other sites

  • Cloud Solutions Architect

If you need to populate ENDDOC for your documents that have images, you can identify and create an overlay file using SQL that will list the last suffixed imagekey for the documents in question. You can use this script:

 

Select D.DocumentKey AS BEGDOC, MAX (ImageKey) AS ENDDOC

from Documents D

join Documentpages P on D.DocID = P.DocID

group by P.DocID, D.DocumentKey

ORDER BY D.DocumentKey ASC

Link to comment
Share on other sites

  • 2 weeks later...
Vaibhav,

 

The production staging database requires an enddoc to be populated. This is due to a logic change on how productions are handled when using image priority.

 

When creating new numbers during a production, this is generated automatically. When using image priority and attempting to use the original image of a document, then that document would require an enddoc so that the production database can be populated with a production enddoc during the staging of the production. The production enddoc is used to determine whether or not the suffix should be used when creating the production image key.

 

If you are using image priority and selecting a production and limiting the selection to only previous productions, then an enddoc should not be required for a document in production set.

 

There should be changes made to the validation process in Eclipse 2016.3.1.

 

Thank you,

Levi Roble

Technical Support Engineer 2

 

Hi Levi,

 

The logic changes like this should be published and not just answered when asked. And changes like this are so critical to the Export/Production Sets, than they should be part of validation.

Link to comment
Share on other sites

Vaibhav,

 

The production staging database requires an enddoc to be populated. This is due to a logic change on how productions are handled when using image priority.

 

When creating new numbers during a production, this is generated automatically. When using image priority and attempting to use the original image of a document, then that document would require an enddoc so that the production database can be populated with a production enddoc during the staging of the production. The production enddoc is used to determine whether or not the suffix should be used when creating the production image key.

 

If you are using image priority and selecting a production and limiting the selection to only previous productions, then an enddoc should not be required for a document in production set.

 

There should be changes made to the validation process in Eclipse 2016.3.1.

 

Thank you,

Levi Roble

Technical Support Engineer 2

 

Hi Levi,

 

The logic changes like this should be published and not just answered when asked. And changes like this are so critical to the Export/Production Sets, than they should be part of validation.

Link to comment
Share on other sites

  • 2 weeks later...
  • IPRO Employee

 

Hi Levi,

 

The logic changes like this should be published and not just answered when asked. And changes like this are so critical to the Export/Production Sets, than they should be part of validation.

 

I agree, it is important to know these changes when running a production/export set. In the latest version of Eclipse, there is now a check in the validation report that checks for 'Missing EndDocs' when running an export.

Link to comment
Share on other sites

  • IPRO Employee

 

Hi Levi,

 

The logic changes like this should be published and not just answered when asked. And changes like this are so critical to the Export/Production Sets, than they should be part of validation.

 

I agree, it is important to know these changes when running a production/export set. In the latest version of Eclipse, there is now a check in the validation report that checks for 'Missing EndDocs' when running an export.

Link to comment
Share on other sites

  • 4 weeks later...

You can simply fill the endoc field with begdoc values.

this applies weather you have images or not. The endoc field is not used to determine the values in the export set. Now with 2016.3.1, you can export a self referencing lfp image load file after filling in the endoc values and use iconvert+ to create a custom load file for begdoc, endoc,begattach, endattach values to overlay back into the case.

this solves the issue if you don't want to use sql or have no access to sql.

not all firm IT departments allow access to sql and the running of custom sql scripts.

Link to comment
Share on other sites

You can simply fill the endoc field with begdoc values.

this applies weather you have images or not. The endoc field is not used to determine the values in the export set. Now with 2016.3.1, you can export a self referencing lfp image load file after filling in the endoc values and use iconvert+ to create a custom load file for begdoc, endoc,begattach, endattach values to overlay back into the case.

this solves the issue if you don't want to use sql or have no access to sql.

not all firm IT departments allow access to sql and the running of custom sql scripts.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...