Search results

Jump to navigation Jump to search
  • [[Profiler Object:Reference|← Profiler Object Reference]] ...y a four-character string. If you are running the Demo version of Profiler Object, the word DEMO will be appended to the build number.
    2 KB (198 words) - 21:19, 19 December 2016
  • ...dicating the number of MatchcodeComponent objects in the current Matchcode object. {{ Object Syntax
    914 bytes (97 words) - 18:52, 7 August 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] ...ofiler Object:Column Specification#AddColumn|AddColumn]]''', '''[[Profiler Object:Column Specification#SetColumnCustomPattern|SetColumnCustomPattern]]''', et
    895 bytes (107 words) - 21:44, 23 February 2015
  • ...ect. If the current Matchcode object was newly created using the [[MatchUp Object:Matchcode:Creation#CreateNewMatchcode|CreateNewMatchcode]] function, then t {{ Object Syntax
    2 KB (231 words) - 19:03, 4 August 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] {{ Object Syntax
    716 bytes (91 words) - 21:46, 23 February 2015
  • This function populates the current instance of the Matchcode object with the settings of the matchcode specified in the character string passed {{ Object Syntax
    1 KB (152 words) - 17:48, 31 July 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] {{Object Parameters2
    2 KB (286 words) - 16:21, 15 May 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] {{Object Parameters2
    2 KB (286 words) - 16:21, 15 May 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] ...for details. They should only be retrieved after calling the '''[[Profiler Object:Profiling#ProfileData|ProfileData]]''' function.
    1 KB (127 words) - 22:07, 23 February 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] ...for details. They should only be retrieved after calling the '''[[Profiler Object:Profiling#ProfileData|ProfileData]]''' function.
    2 KB (176 words) - 22:06, 23 February 2015
  • ...lication can no longer add more records to the key file with the [[MatchUp Object:Read-Write:Match Key#WriteRecord|WriteRecord]] function. This function takes every record passed via the [[MatchUp Object:Read-Write:Match Key#WriteRecord|WriteRecord]] function and passes them thr
    711 bytes (92 words) - 23:44, 27 July 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] {{Object Parameters2
    3 KB (294 words) - 16:34, 15 May 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] {{Object Parameters2
    3 KB (300 words) - 16:33, 15 May 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] {{Object Parameters2
    3 KB (352 words) - 16:24, 15 May 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] They should only be retrieved after calling '''[[Profiler Object:Profiling#Profile Data|ProfileData]]''' function.
    2 KB (266 words) - 22:06, 23 February 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] {{Object Parameters2
    4 KB (428 words) - 16:22, 15 May 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] ...for details. They should only be retrieved after calling the '''[[Profiler Object:Profiling#ProfileData|ProfileData]]''' function.
    4 KB (418 words) - 22:07, 23 February 2015
  • {{ Object Syntax |Syntax=StringValue =mdMC->GetDescription()
    2 KB (239 words) - 18:51, 7 August 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] These statistics should only be retrieved after calling the '''[[Profiler Object:Profiling#ProfileData|ProfileData]]''' function. These values are all colum
    6 KB (732 words) - 22:02, 23 February 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] ...for details. They should only be retrieved after calling the '''[[Profiler Object:Profiling#ProfileData|ProfileData]]''' function.
    5 KB (612 words) - 00:39, 25 February 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] Theses statistics should only be retrieved after calling the '''[[Profiler Object:Profiling#ProfileData|ProfileData]]''' function. These values are all colum
    13 KB (1,456 words) - 22:01, 23 February 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] Theses statistics should only be retrieved after calling the '''[[Profiler Object:Profiling#ProfileData|ProfileData]]''' function. These values are all colum
    8 KB (926 words) - 22:05, 23 February 2015
  • {{ Object Syntax |Syntax=int = mdMC->GetMappingItemCount()
    2 KB (277 words) - 18:54, 7 August 2015
  • ...insert, update, or delete matchcode components from the current Matchcode object. This function accepts a MatchcodeComponent object as its only argument and adds this component as the last component for this
    4 KB (515 words) - 19:03, 4 August 2015
  • {{ Object Syntax |Syntax=int = mdMC->CreateNewMatchcode(MatchcodeName)
    808 bytes (104 words) - 17:46, 31 July 2015
  • ...string value indicating the file path to the folder containing the MatchUp Object files. {{ Object Syntax
    3 KB (309 words) - 22:01, 19 December 2016
  • [[Profiler Object:Reference|← Profiler Object Reference]] ...for details. They should only be retrieved after calling the '''[[Profiler Object:Profiling#ProfileData|ProfileData]]''' function.
    5 KB (539 words) - 22:06, 23 February 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] {{Object Parameters3
    3 KB (423 words) - 16:23, 15 May 2015
  • ...he input data and use it to generate match keys according to the [[MatchUp Object:Hybrid:Mapping|mapping]] and the selected matchcode. {{ Object Syntax
    3 KB (437 words) - 00:29, 8 August 2015
  • ...tion cannot be called until after the application has called the [[MatchUp Object:Read-Write:Processing#Process|Process]] function. {{ Object Syntax
    5 KB (627 words) - 18:39, 7 August 2015
  • ...o the key file if no duplicate was found by the last call to the [[MatchUp Object:Incremental:Comparison#MatchRecord|MatchRecord]] function. It is also used {{ Object Syntax
    1 KB (163 words) - 17:12, 13 October 2017
  • {{ Object Syntax |Syntax=mdMU->ClearFields()
    4 KB (548 words) - 00:49, 8 August 2015
  • If it is not a duplicate, a typical program would call the [[MatchUp Object:Incremental:Key File#AddRecord|AddRecord]] function to add this key to the {{ Object Syntax
    5 KB (722 words) - 00:49, 8 August 2015
  • {{ Object Syntax |Syntax=mdMU->ClearMappings()
    3 KB (385 words) - 20:26, 5 August 2015
  • ...acters in a key generated using the matchcode selected using the [[MatchUp Object:Hybrid:Initialization#SetMatchcodeName|SetMatchcodeName]] function. {{ Object Syntax
    4 KB (512 words) - 00:24, 8 August 2015
  • {{ Object Syntax |Syntax=mdMU->ClearMappings()
    3 KB (402 words) - 20:39, 5 August 2015
  • {{ Object Syntax |Syntax=mdMU->ClearMappings()
    3 KB (408 words) - 20:27, 5 August 2015
  • ...ctions and the matchcode defined when the Read/Write deduper was [[MatchUp Object:Read-Write:Initialization|initialized]]. ...all values from previous calls to the [[#AddField|AddField]] or [[MatchUp Object:Read-Write:Retrieval#ReadRecord|ReadRecord]] function. The application shou
    4 KB (659 words) - 16:41, 7 August 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] ...lumn you intend to profile. All columns must be added before '''[[Profiler Object:Initiate Profiling#StartProfiling|StartProfiling]]''' is called.
    12 KB (1,374 words) - 18:59, 3 March 2015
  • [[Profiler Object:Reference|← Profiler Object Reference]] The table-based statistics should only be retrieved after '''[[Profiler Object:Profiling#ProfileData|ProfileData]]''' is called.
    10 KB (1,137 words) - 16:36, 15 May 2015
  • ...interface to use transactions, processing multiple calls to the [[MatchUp Object:Incremental:Key File#AddRecord|AddRecord]] function before committing the c ...on tells MatchUp Object to wrap subsequent multiple calls to the [[MatchUp Object:Incremental:Key File#AddRecord|AddRecord]] function with a transaction bloc
    4 KB (517 words) - 20:31, 30 July 2015
  • [[Email Object|← Email Object]] Email Object known issues.
    1 KB (166 words) - 22:45, 15 December 2016
  • This function returns the component type of the current MatchcodeComponent object. ...eturn value for this function is an enumerated value of the type [[MatchUp Object:Enumerations#MatchcodeComponentType|MatchcodeComponentType]].
    9 KB (1,246 words) - 00:12, 8 August 2015
  • {{ Object Syntax |Syntax=mdMU->SetPathToNameFiles(char)
    9 KB (1,174 words) - 21:49, 19 December 2016
  • [[Profiler Object:Reference|← Profiler Object Reference]] This function sets the License Key required to enable Profiler Object’s complete functionality.
    13 KB (1,527 words) - 21:18, 19 December 2016
  • ...s section set the values for the various settings of a matchcode component object. They can be used to construct new matchcode components when adding them to This function specifies the type for the current MatchcodeComponent object.
    11 KB (1,436 words) - 00:19, 9 April 2022
  • {{ Object Syntax |Syntax=mdMU->SetPathToMatchUpFiles(char)
    11 KB (1,423 words) - 21:54, 19 December 2016
  • [[Profiler Object:Reference|← Profiler Object Reference]] {{Object Parameters2
    10 KB (1,294 words) - 18:41, 6 March 2019
  • [[Email Object|← Email Object]] ==How do I automate the installation of the Email Object?==
    5 KB (797 words) - 23:26, 27 December 2019
  • [[Profiler Object:Reference|← Profiler Object Reference]] ...me amount of upward compatibility, as new column types can be added to the object without requiring the developers to update and rebuild their applications.
    9 KB (928 words) - 21:43, 25 February 2015
  • {{ Object Syntax |Syntax=mdMU->SetPathToMatchUpFiles(char)
    11 KB (1,478 words) - 21:47, 19 December 2016
  • [[Profiler Object:Reference|← Profiler Object Reference]] The column-based statistics should only be retrieved after '''[[Profiler Object:Profiling#ProfileData|ProfileData]]''' is called. These functions return co
    25 KB (2,887 words) - 17:37, 22 September 2023
  • !Protocol !! Syntax !Protocol !! Syntax
    5 KB (664 words) - 19:18, 7 December 2018
  • !Protocol !! Syntax !Protocol !! Syntax
    5 KB (725 words) - 21:36, 18 March 2020
  • !Protocol !! Syntax !Protocol !! Syntax
    15 KB (1,990 words) - 00:58, 23 November 2021
  • !Protocol !! Syntax !Protocol !! Syntax
    14 KB (1,865 words) - 22:47, 2 May 2016
  • [[RightFielder Object|← RightFielder Object]] syntax and examples on how to do this.
    3 KB (493 words) - 18:18, 18 November 2019
  • !Protocol !! Syntax !Protocol !! Syntax
    21 KB (2,768 words) - 00:34, 11 June 2022
  • !Protocol !! Syntax !Protocol !! Syntax
    46 KB (6,225 words) - 23:38, 26 February 2024
  • [[Email Object|← Email Object]] *https://releasenotes.melissa.com/on-premise-api/email-object/
    8 KB (1,279 words) - 01:27, 7 March 2023
  • !Protocol !! Syntax !Protocol !! Syntax
    18 KB (2,534 words) - 01:16, 21 January 2023
  • |Data Type||The type of data used by this component. See [[MatchUp Object:Matchcodes#Matchcode Components|Matchcode Components]] for a list of all av For more information these settings, see [[MatchUp Object:Component Properties|Component Properties]].
    9 KB (1,468 words) - 18:18, 8 April 2022
  • Because the CREATE TRIGGER syntax has no accommodation for parameters, you cannot specify the name of a confi [[Category:MatchUp Object]]
    5 KB (685 words) - 18:19, 16 July 2015
  • !Protocol !! Syntax !Protocol !! Syntax
    36 KB (4,869 words) - 19:32, 4 December 2023
  • [[RightFielder Object|← RightFielder Object]] ...ructions of available tables and types which can be overridden, as well as syntax and examples, open the mdRightFielder.cfg in a text editor and follow the i
    11 KB (1,733 words) - 15:59, 13 May 2016
  • Currently, our email object only performs normal email validation which is essentially just a simple sp Mailbox validation will only occur if the email passes our domain level and syntax level checks.
    14 KB (2,311 words) - 00:53, 24 February 2022
  • Currently, our email object only performs normal email validation which is essentially just a simple sp Mailbox validation will only occur if the email passes our domain level and syntax level checks.
    11 KB (1,904 words) - 19:07, 10 January 2020
  • |Image=[[Image:ICON_API_AddressObject.png|84px|Address Object|link=#Address Object]] |Link=[[#Address Object|Address Object]]
    128 KB (19,482 words) - 23:27, 19 February 2024
  • |Syntax Changed |The syntax of the submitted email address was changed.
    90 KB (14,655 words) - 23:27, 19 February 2024
  • ...the input data, or used a similar product, such as Melissa Data's Address Object or WebSmart Address Verifier service, you may have an Address Key available ...of GeoCoding precision is based on your subscription level to the GeoCoder Object or the WebSmart GeoCoding Service, depending on your processing type (On-Pr
    43 KB (6,888 words) - 19:26, 21 August 2012