Is there an easy way to resolve this translations ...
# sdf
n
Is there an easy way to resolve this translations limitation on Copy to Account? This account doesn't use translations but it pops up on different Copy to Account attempts. This is a 'quick' need to bring across a CSV Import:
Copy code
Unable to copy object. Object custimport_assembly_import being copied is dependent on object custtab_anz_item_aus_reporting that uses translations, which is functionality that is not supported by the Copy to Account feature.
Here is a different one on an Assembly item "customrecord_2663_entity_bank_detail" how does a field like that interfere with an Item Import's Copy to Account?
a
I'm not defending how dumb this is, but presumably the form used for the import has a reference to that record (its a record not a field) and so it does a dependency check against ALL THE THINGS and if it thinks anything is not cool it will just say nope. you can probably do this with actual SDF, (as opposed to copy to account) you'd just have to tweak with some things, maybe add dependencies in the manifest and such to work around it. you can also potentially just create a NEW simplified form in your source account, strip out a bunch of fields on the form (and tabs and anything else you can remove tbh) and update your import to use THAT form just so you can Xfer it over to the target account (meaning still using copy to account as opposed to SDF)
n
that's absolutely a good way to do it. thanks for the concept.
goodluck 1
243 Views