Recently it has been brought to my attention that all but one of the custom fields we wanted to be present in a ledger entry record do not have any values filled in. I understand I need to add Field Mapping logic but, when I tried this in a test environment for one checkbox custom field, ledger records were created for all payments when this custom field was ever checked. I would like to avoid this. If I use mapping behavior point-in-time instead of current value, will I avoid creating ledger records for anytime a relevant value was in place and have it simply work for new ledger entry records?
Hi Melanie, yes pit mapping ensures that ledger records are only created when the checkbox has a relevant value at the time a ledger entry is created. This way, you wont end up with extra ledger records for every time the checkbox is checked, and it will only apply to new or updated entries.
