In some scenarios the unique field to compare with is a calculated field. I would want to prevent duplicate by comparing the imported record field with the calculated existing field. However - I can’t select calculation fields to check for duplicates.
I would love this as well. I would have no need to bring in imported data to that calc field. Just to compare during the import process if the data from excel is an exact match to anything existing in Tape already based on that calc field.
That said, I’ve been surviving fine with a simple workaround here. Obviously true features are always nicer than workarounds…
But it isn’t too hard to start by doing an export from tape with the record ID and the desired calc field included.
Then upload that calc field data into a temporary text field for the matching Tape record ID’s.
Then import your new data, with mapping to that text field, for dupe check purposes.
Then delete out that temporary text field once finished.
Obviously not ideal if you need a workaround like that every single time. But if it’s for one-off/critical situations, it’s a usable and effective workaround.
I sure wish I could have more feature request votes to add support on great requests like this.
Do you guys check to make sure that you take your votes back from items that I have already been implemented? I found out that I had a bunch of votes still attached to features that were already released.