VERIFIED SOLUTION i

CONFIRM: Inspection not exporting with the error "The 'http://www.wrcplc.co.uk/Schemas/ETON:InspectionDefectReason' element is invalid"

Product Feature: Street Works

Operating System: Windows 2008

Database: Oracle, SQL Server
 

Issue

Inspection not exporting with the error "The 'http://www.wrcplc.co.uk/Schemas/ETON:InspectionDefectReason' element is invalid"

Getting error exporting an inspection with the following being shown: Inspection flagged to 'Export Failed'. Error: The 'http://www.wrcplc.co.uk/Schemas/ETON:InspectionDefectReason' element is invalid - The value 'Around ASP temporary bitmac has been used and the grass verge has sunk. Replace temporary bitmac with permanent on footway and rectify top soil and seed required on grass verge. Please attend site meeting on Tuesday 10th February 2015 at 11:00AM. If this is not convenient please contact Pitny Bowes on 000000000000 to rearrange. Defect joint inspections are required as per the Code of Practice (CoP) within 10 WORKING DAYS OF RECEIPT OF DEFECT. If no response is made you will be charged with failure to comply.' is invalid according to its datatype 'String' - The actual length is greater than the MaxLength value.

Upon making the notes field shorter in Confirm, the inspection continues to fail to export and give the exact same error. 


User-added image



 

Cause

The issue is due to the text entered in Inspection Items, not in the Defect Notes or Inspection Notes or Comments.

Resolution

UPDATED: March 22, 2017

The issue is due to the text entered in Inspection Items, not in the Defect Notes or Inspection Notes or Comments. 

Click on the Items tab of the Inspection and see the text entered against the Inspection Item. If it is more than 500 charatcters, then shorten it to less than 500 characters.

Click OK and make some changes in Defect Notes or Comments so that we can save the Inspection to Re-export it. 

Run the Task Processor and the Inspection should get exported successfully.