Reporting issues resolved in KTA 7.5 Fix Packs

Question / Problem: 

What issues related to reporting have been resolved in KTA 7.5 Fix Packs?

Answer / Solution: 

The following reporting issues are included in the release notes of the listed fix pack (unless noted with *).  If encountering an issue with reporting, it is best to update to the latest fix pack so that all cumulative fixes are applied.

• 7.5.0.30
  • 1618335 Case 26314011: Automatic identity reseed for status_kc_doc_field truncates unprocessed reporting field data
• 7.5.0.29
  • 1582417 Case 25043583: The DELETE statement conflicted with the REFERENCE constraint
  • 1573629 Case 26239055: Field changes do not show up in Kofax Analytics For TotalAgility
    • Introduced by the “Reclassification affects field reporting data” fix, PDF/DC/IP activities inappropriately changed fields to be reported as “system extracted”, thus field_accum_fact.field_recog_status_key was set incorrectly, and so fields did not show as changed in KAFTA reports.
  • 1567482 Case 26239055, 26243378: Field Reporting data can be lost after PDF/DC/IP activities
    • Introduced by the “Reclassification affects field reporting data” fix, PDF/DC/IP activities inappropriately report that no fields are present, thus even if a current field value is reported again by a subsequent activity, it would have lost reporting data such as original value, confidence, etc.
  • 1564431 Case 26218684: Reporting performance issue with doc_accum_fact table
  • *Bug 1573034:[7.5.0.29] [Reporting] 'Error mapping data row MapStatusKcDocField ' occurs in Reporting log
• 7.5.0.28
  • 1558016 Case 26193760: Reporting: Problematic messages causing ETL to complete without processing any message
• 7.5.0.27
  • 1545034 Case 26176670: Duplicate entry in Reporting tfs_class_dim table causes Reporting ETL failure “The MERGE statement attempted to UPDATE or DELETE the same row more than once    
  • 1542389 Case 26189941: Error during data extraction on message using reverted compressed flag: Invalid character in the given encoding
• 7.5.0.26
  • 1530838 Case 26172354: [Reporting] extr_batch_sess_key reported after confirmation field  
  •  1524240 Case 26172354: Reclassification affects field reporting data
    • Scenario 1: If a document is reclassified after extraction, such as in Validation, reporting data for fields of the previous type will persist and be associated with a document type that does not have those fields. This causes KAFTA reports to show fields that do not belong to the given document type.
    • Scenario 2: If a document is reclassified from a type where a field has “Include in analytics” is yes to a type where the same field has “Include in analytics” is no, then the reporting data for the field will persist. In KAFTA this causes this field inappropriately show up on a type where it isn't intended to be reported on. It also has the appearance of sporadic behavior, because it will only happen when the document is reclassified from a type where the field is reported on.
• 7.5.0.25
  • 1509939 Case 26140031: Support changing reporting variable in DatabaseCmdTimeoutSec in v7.5.0.x
    • More details: Increasing Timeouts used by the KTA Reporting Service - DatabaseCmdTimeoutSec
  • 1500883 Case 26157068: Reporting data: Original value and confidence not set
  • 1496170 Case 26135941: Extr_batch_ses_key isn't reported in field_accum_fact table
• 7.5.0.23
  • 1461143 Case 26116779: Reporting: Error data transformation task TransformStatusKcDoc  
  • 1452925 Case 26084690: Reporting - Error PerformUpdates task - Execution Timeout Expired 
• 7.5.0.21
  • 1396585 Case 26058595: Reporting stops processing messages in wsa_messages if the orphaned entries count is bigger than default number of processed records (1500)  
• 7.5.0.19
  • 1373937 Case 25051197: The MERGE statement attempted to UPDATE or DELETE the same row more than once
    • More details: Merge Exception from Reporting function LoadEventDataDim.PerformUpdates
  • 1369116 Case 25064261: Reporting data stuck in WSA_MESSAGES table with error "TryDeserializeWithPatchingXml spent more than 1000 cycles" 
    • Note: despite the name of the bug, no error is logged for this problem.  Instead the service hangs with no further processing or log output.
• 7.5.0.17
  • 1327287 Case 25056955: [Reporting] Confirming table cells without modification shows as a changed field
• 7.5.0.16
  • 1319589 Case 25041119, 25056138: Timeout Issues Related To Kofax Reporting Causing SQL Performance Problems
• 7.5.0.14
  • *1306384: Performance degradation between KTA 7.5.0.11 and 7.5.0.12 with frequent spikes in response times
• 7.5.0.13
  • 1299446 Case 25034013: Some reported field should contain the symbols which are not allowed in XML
  • 1295368 Case 25040416: Document type with apostrophe is causing the reporting system task to fail
  • 1294724 Case 25040509: Arithmetic overflow error converting IDENTITY to data type int
  • 1293316 Case 25028123: Reporting system task fails with error "Violation of UNIQUE KEY constraint 'user_logon_name_user_type_uq'. Cannot insert duplicate key in object 'dbo.user_dim'"
• 7.5.0.12
  • 1286204 Case 25036079: Reporting - apostrophe to a folder name causing Unclosed quotation mark after the character string ' '
• 7.5.0.8
  • 1238225 Case 25010893: Reporting Service fail with apostrophe in resource user name
• 7.5.0.6
  • 1214937 Case 25001973: Reporting data not linking with pre-7.5 data
• 7.5.0.5
  • 1209224 Case 24082899: Cannot insert duplicate key row in object 'dbo.field_accum_fact' with unique index 'idx_faf_pk_lkp'.
• 7.5.0.4
  • *1195308: Reporting: 'Exception: Transaction (Process ID 67) was deadlocked on lock resources(...)' occurs in log
  • *1196183: Performance Issue: Excessive calls for selecting values for path_dim appears in Reporting
• 7.5.0.3
  • 1191586 Case 24088423: Reporting: After upgrading to v7.5, Kofax TotalAgility reporting throws the error - "Error during Deserialize: There is an error in XML document."
• 7.5.0.2
  • *1184705: 'Exception: A MERGE statement cannot UPDATE/DELETE the same row of the target table multiple times' occurs in Reporting logs
• 7.5.0.1
  • 1149132 Case 24061127: SQL timeouts on Update batch_accum_fact from Kofax.CEBPM.Reporting.AzureETL.
  • *1169524: Document Review does not properly report time against each document in doc_sess_snapshot_fact.doc_sess_duration_ms
  • *1169525: Classification activity sometimes creates 2 system classification events