Query s tmp apostrophe in comment: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m Text replacement - "| DIC_app" to "| DIC_timing = complete always | DIC_app"
m Text replacement - "DIC_timing = complete always" to "DIC_timing ="
Line 3: Line 3:
| DIC_related_concepts = [[S Tmp]]
| DIC_related_concepts = [[S Tmp]]
| DIC_firmness = hard check  
| DIC_firmness = hard check  
| DIC_timing = complete always
| DIC_timing =
| DIC_app = CCMDB.mdb
| DIC_app = CCMDB.mdb
| DIC_coding = query ''s_tmp_apostrophe_in_comment''
| DIC_coding = query ''s_tmp_apostrophe_in_comment''

Revision as of 11:57, 25 September 2018

Data Integrity Checks
Summary: There must not be apostrophes in the comment field as they would mess with Julie's data analysis.
Related: [[S Tmp]]
Firmness: hard check
Timing:
App: CCMDB.mdb
Coding: query s_tmp_apostrophe_in_comment
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: 2016-Jun-02
Backlogged: true
  • Cargo


  • SMW
"CCMDB.mdb" is not in the list (SAP, not entered, Centralized data front end.accdb, DSM Labs Consistency check.accdb, CCMDB.accdb, TISS28.accdb) of allowed values for the "DICApp" property. 
  • Categories:  
  • form:

Implementation date would have been before this, but that is when a tweak is mentioned in logs. .