Search results

• Pentaho:Contact Verify:GeoCode
  ..., and by invisible boundaries such as city, town, township, county limits, property lines, and short, imaginary extensions of streets and roads. [[Category:Pentaho]]
  8 KB (1,305 words) - 00:16, 28 May 2015
• Pentaho/Contact Zone:Contact Verify:GeoCode
  ..., and by invisible boundaries such as city, town, township, county limits, property lines, and short, imaginary extensions of streets and roads. [[Category:Pentaho]]
  8 KB (1,312 words) - 17:32, 11 January 2017
• Contact Zone:Build History
  *Platform updated to Pentaho 6.1 :*Property
  8 KB (1,085 words) - 21:14, 27 October 2017
• Pentaho:MatchUp:Matchcodes
  ..., then the absence of data in both records would indicate a match. If this property is off, then two records with missing data, but matching in every other way [[Category:Pentaho]]
  19 KB (2,918 words) - 22:06, 15 June 2015
• Pentaho/Contact Zone:MatchUp:Matchcodes
  ..., then the absence of data in both records would indicate a match. If this property is off, then two records with missing data, but matching in every other way [[Category:Pentaho]]
  19 KB (2,924 words) - 20:49, 11 January 2017
• Result Code Details
  ...84px|Data Quality Components for Pentaho|link=#Data Quality Components for Pentaho]] ...k=[[#Data Quality Components for Pentaho|Data Quality<br>Components<br>for Pentaho]]
  128 KB (19,482 words) - 23:27, 19 February 2024
• MatchUp Object:FAQ
  ...reporting and many other database tools. It is also available as a SSIS or Pentaho Contact Zone component for enterprise level needs. ...ned after processing and calling the ReadRecord method and the GetUserInfo property. In addition, GetResults(), GetCount(), and GetEntry() give you post proces
  28 KB (4,493 words) - 00:45, 26 March 2022

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)