Search results

• MatchUp Object:Matchcodes
  The matchcode component should match the data type that MatchUp Object needs to build the match key deduping, the matchcode would use the last name component. At the programming stage,
  8 KB (1,184 words) - 22:19, 5 August 2015
• MatchUp Object:Important
  ...in an existing previously installed MatchUp Object. Therefore, some of the Global examples will not run unless you swap in the new matchcode file, or add the This version separates MatchUp Object into two distinct products - Global and Domestic (US and Canada).
  8 KB (1,178 words) - 19:01, 1 May 2020
• Salesforce:Build History
  ...ns of lightning for compatibility with our on-page Express Entry Lightning component. Package is no longer required so removed from pre-requisite package requir *Global Email Batch - Fixed bug where only partial datasets were being passed for v
  8 KB (1,237 words) - 01:02, 8 March 2023
• Salesforce:FAQ
  ...ry: [[Listware for Salesforce:Express Entry Component#Mobile|Express Entry Component - Mobile]]. The rest of the components in Salesforce rely on Visualforce pa ...t) when they use the Update functionality within the Personator and Global Address Verification components.
  3 KB (475 words) - 23:52, 26 December 2019
• Legacy:Salesforce:FAQ
  ...egacy:Listware for Salesforce:Express Entry Component#Mobile|Express Entry Component - Mobile]]. The rest of the components in Salesforce rely on Visualforce pa ...t) when they use the Update functionality within the Personator and Global Address Verification components.
  3 KB (478 words) - 23:36, 27 December 2019
• FAQ:SSIS:Known Issues
  If using SSIS 2014 BusinessCoder component for SSIS, we recommend to use Visual Studio 2013 per Melissa’s SSIS Syste ...used in correlation with SQL Server 2014. Which causes the BusinessCoder component not to appear in the SSIS Toolbox.
  13 KB (1,972 words) - 22:54, 7 June 2023
• Pentaho/Contact Zone:Global Verify:Address
  ...or addresses. Use this to select the database fields that will contain the address data to be verified and standardized. ==Address Input Fields==
  7 KB (1,041 words) - 17:53, 11 January 2017
• Contact Zone:Global Verify:Output Address
  The Output Address Columns tab contains the mappings for your output data. ...organization input field. It is not modified or populated by Global Verify Component.
  4 KB (567 words) - 00:13, 5 January 2017
• Salesforce:Getting Started
  ...leanSuite lookups mapped to them. For instance, you may have Global Email, Global Phone, and Personator Lookups all mapped to the Contact object. ...reenshot below we can see a Personator Contact Mapping named <code>Mailing Address Verification</code>. The input column on the left specifies which data to s
  9 KB (1,431 words) - 17:28, 22 September 2023
• Legacy:Salesforce:Setup
  For each object, you’ll need to specify which fields contain the name, address, phone, and email. This can be configured under the Advanced Mappings tab. *These input/output map settings will be used in the Personator/Global Address Verification/Property components as well as the when doing batch processing
  4 KB (563 words) - 01:08, 13 March 2021
• Salesforce:Getting Started with Lightning Components
  ...ion), take a look at [[Salesforce:Lightning Global Express Entry|Lightning Global Express Entry]]. Otherwise, follow these instructions to create a new mappi
  2 KB (392 words) - 01:16, 13 March 2021
• FAQ:SSIS:Data Quality Components
  *Copy of Component DLLS: *Component Pipeline Dlls:
  10 KB (1,551 words) - 22:27, 20 August 2020
• Pentaho:Global Verify:Address
  ...or addresses. Use this to select the database fields that will contain the address data to be verified and standardized. ==Address Input Fields==
  7 KB (1,034 words) - 21:16, 9 June 2015
• Unison:US Address Verification
  The Unison by Melissa Address Object cleanses contact data. This section displays the possible inputs for the Address Service. An address and ZIP code are required.
  14 KB (2,132 words) - 17:58, 15 March 2024
• SSIS:Global Verify:Address
  ==Advisory - Global Verify Address On Premise - 32bit mdGlobalAddr.dll deprecation== ...32bit dll Deprecation|SSIS Global Verify Address On Premise Users – Global Address Object 32bit dll Deprecation]].
  17 KB (2,727 words) - 01:45, 29 November 2022
• SSIS:MatchUp:Component Properties
  !Component |The street number from an address line [3]
  17 KB (2,657 words) - 22:09, 10 February 2017
• Listware for Excel:Build History
  *Add a Region button to change between US & Canada and Global regions. *US Check: Add MAK (unique Melissa Address Key) and BaseMAK fields.
  10 KB (1,371 words) - 00:34, 1 June 2023
• Returned Result Codes:Enterprise Solutions
  |[[Returned Result Codes:APIs#Address Object|Address Object]] |[[Returned Result Codes:APIs#Global Address Object|Global Address Object]]
  39 KB (5,907 words) - 22:40, 3 June 2019
• Data Quality Suite:Build History
  For a specific build history of a Data Quality Suite Component, see the links below. *[[Build History:Address Object|Address Object Build History]]
  12 KB (1,911 words) - 01:00, 13 January 2021
• Result Code Examples
  |[[#Address|Address]] .......................... |[[#Phone / Global Phone|Phone / Global Phone]] ...
  9 KB (1,162 words) - 23:30, 7 September 2023

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