If you have a comment on this topic, contact Aptify Documentation. If you want to return to the Aptify Community Site, please click here.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

To write a duplicate check object in Aptify, a developer writes code that implements the IAptifyDuplicateCheck interface to define the criteria for absolute and/or potential matches. IAptifyDuplicateCheck is an interface in the Aptify.Framework.BusinessLogic.GenericEntity namespace (see the Aptify Software Development Kit for more information on this interface).
Also, the code typically references a stored procedure that contains the match logic. As described in "Use Stored Procedures to Retrieve Database Values" in the Developer Guide, Aptify recommends that developers use stored procedures where possible rather than include SQL statements directly within a plug-in object's code.
The IApifyDuplicateCheck interface has two members that serve the following purposes:

  • CheckForDuplicates Method: This method is responsible for checking for duplicate records against the data in the pending record within the current GE. Aptify recommends that you use a parameterized data table to provide input values for a stored procedure that contains the matching logic. Based on the data table created by the stored procedure's execution, the method then returns a duplicate check result (None, Potential, or Exact) and the set of Duplicate record IDs.
  • DuplicateMessageObject Property: This property identifies the object that corresponds to the duplicate message dialog to display when the CheckForDuplicate method has identified one or more duplicate record matches. To use the standard message box provided by Aptify (whose functionality and appearance is described in "Types of Duplicates Identified" on page 240), this property should return Nothing. See the sample duplicate check objects for an example.

This topic contains the following sub-topics:
<child display>

  • No labels