Help

Save the date! Join us on October 16 for our Product Ops launch event. Register here.

John_inNJ
6 - Interface Innovator
6 - Interface Innovator
since ‎Oct 15, 2018
‎Nov 29, 2022

User Statistics

  • 13 Posts
  • 0 Solutions
  • 0 Kudos given
  • 11 Kudos received

User Activity

Since calculated fields cannot be merged, why have them appear at all in the dedupe interface? If you have a lot of calculations it’s a lot of clutter.
I wish the field order in dedupe was useful. Putting them in order of creation is not helpful when you have hundreds of fields.
you can’t merge a calculated field so why to they appear in the “Dedupe” app. In my case I have scores of calculations so using dedupe is difficult because I can’t hide those non-mergable calculation fields.
Since calculated fields cannot be merged, why have them appear in the dedupe block’s merge interface? If you have a lot of calculated fields it’s a lot of clutter with no purpose.
The Dedupe block seems to match black fields. This makes the Dedupe block not very useful. Is there anyway to exclude blank fields?