[APEXMALHAR-2353] timeExpression should not be null for time based Dedup

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.6.0
• Assignee: Bhupesh Chawda
• Reporter: Bhupesh Chawda
• Created: 23/Nov/16 08:21
• Updated: 02/Dec/16 21:12
• Resolved: 23/Nov/16 12:17

Description

Time Based Dedup has timeExpression as optional. It has to be supplied by the user.

In the current setting, if the user does not specify a timeExpression, then a different time (System time) will be passed for each tuple, irrespective of whether the tuple is a duplicate or a unique. This is a bug since even the duplicate tuples may fall in different buckets and will be concluded as unique.

Issue Links

• links to: GitHub Pull Request #508