Search results

• Pentaho/Contact Zone:Basics
  A basic Pentaho/Contact Zone Data Transform consists of an Input, a Data Transform (the MD ==Property Component==
  3 KB (409 words) - 23:46, 17 January 2017
• Pentaho/Contact Zone:Property Value Output
  ...ups and columns. For a list of codes returned by these columns, refer to [[Property Codes]]. These fields contain data on the current value of the property.
  8 KB (1,259 words) - 22:13, 11 January 2017
• Pentaho/Contact Zone:Property:Advanced Configuration
  ====Property Web Service==== [[Category:Pentaho]]
  3 KB (440 words) - 22:06, 11 January 2017
• Pentaho/Contact Zone:Building Output
  ...ups and columns. For a list of codes returned by these columns, refer to [[Property Codes]]. These fields contain data on the physical dimensions of the entire property.
  10 KB (1,608 words) - 22:13, 11 January 2017
• Pentaho/Contact Zone:Property:Input
  [[Category:Pentaho]] [[Category:Property Component]]
  971 bytes (147 words) - 22:08, 11 January 2017
• Returned Result Codes
  ...Solutions#Data Quality Components for Pentaho|Data Quality Components for Pentaho]] |[[Returned Result Codes:Web Services#Property|Property]]
  4 KB (597 words) - 20:02, 13 January 2015
• Pentaho:Business Coder:Output
  :The city associated with the property address (CHICAGO, ATLANTA, DENVER). [[Category:Pentaho]]
  3 KB (470 words) - 22:49, 27 September 2016
• Returned Result Codes:Legacy Services
  ...Solutions#Data Quality Components for Pentaho|Data Quality Components for Pentaho]] |[[Returned Result Codes:Web Services#Property|Property]]
  11 KB (1,542 words) - 22:23, 3 March 2015
• Pentaho/Contact Zone:Business Coder:Output
  :The city associated with the property address (CHICAGO, ATLANTA, DENVER). [[Category:Pentaho]]
  3 KB (473 words) - 23:08, 10 January 2017
• Returned Result Codes:Software
  ...Solutions#Data Quality Components for Pentaho|Data Quality Components for Pentaho]] |[[Returned Result Codes:Web Services#Property|Property]]
  10 KB (1,482 words) - 19:57, 13 January 2015
• Returned Result Codes:APIs
  ...Solutions#Data Quality Components for Pentaho|Data Quality Components for Pentaho]] |[[Returned Result Codes:Web Services#Property|Property]]
  12 KB (1,677 words) - 23:04, 18 September 2019
• Returned Result Codes:Web Services
  ...Solutions#Data Quality Components for Pentaho|Data Quality Components for Pentaho]] |[[#Property|Property]]
  20 KB (2,887 words) - 17:38, 29 September 2017
• Returned Result Codes:Enterprise Solutions
  |[[#Data Quality Components for Pentaho|Data Quality Components for Pentaho]] |[[Returned Result Codes:Web Services#Property|Property]]
  39 KB (5,907 words) - 22:40, 3 June 2019
• Pentaho:MatchUp:Component Properties
  ...s property determines where MatchUp begins counting when applying the Size property. ...aces from the beginning of a piece of data, the end or both. Usually, this property is always enabled.
  13 KB (2,056 words) - 21:16, 28 October 2016
• Pentaho/Contact Zone:MatchUp:Component Properties
  ...s property determines where MatchUp begins counting when applying the Size property. ...aces from the beginning of a piece of data, the end or both. Usually, this property is always enabled.
  13 KB (2,062 words) - 20:57, 11 January 2017
• Pentaho:MatchUp:Expression Elements
  ...True. If a package is running using the DTExec command prompt utility, the property is set to False. [[Category:Pentaho]]
  15 KB (2,340 words) - 20:02, 16 September 2016
• Pentaho/Contact Zone:MatchUp:Expression Elements
  ...True. If a package is running using the DTExec command prompt utility, the property is set to False. [[Category:Pentaho]]
  15 KB (2,346 words) - 20:48, 11 January 2017
• 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 100 | next 100) (20 | 50 | 100 | 250 | 500)