# Advance Mapping Only perform mapping when:- (Checkbox exception case)

**URL:** <https://connective.celigo.com/t/advance-mapping-only-perform-mapping-when-checkbox-exception-case/614>\
**Category:** Integrator.io\
**Tags:** mapper, handlebars\
**Created:** [November 8, 2022, 12:42pm UTC](https://connective.celigo.com/t/advance-mapping-only-perform-mapping-when-checkbox-exception-case/614 "2022-11-08T12:42:17Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yashkumar](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/yashkumar/32/9271_2.png) [@yashkumar](https://connective.celigo.com/u/yashkumar)\
**Post date:** [November 8, 2022, 12:42pm UTC](https://connective.celigo.com/t/advance-mapping-only-perform-mapping-when-checkbox-exception-case/614/1 "2022-11-08T12:42:17Z")

</div>

Hello All,

This feature allow us to define when a mapping should be performed without using handlebars. The offered options are:-

Perform mapping while:-

- Creating a record.
- Destination record being updated does not have a value for this field
- Source Record has a value
- Updating a record.

Note - From my observation, The option "Destination record being updated does not have a value for this field" will not be applicate to destination checkbox fields As a checkbox always carries a value (either True or False).

---

<div class="post-metadata">

**Author:** ![courtneyjordan](https://avatars.discourse-cdn.com/v4/letter/c/b2d939/32.png) [@courtneyjordan](https://connective.celigo.com/u/courtneyjordan)\
**Post date:** [November 8, 2022, 5:28pm UTC](https://connective.celigo.com/t/advance-mapping-only-perform-mapping-when-checkbox-exception-case/614/2 "2022-11-08T17:28:34Z")

</div>

Hi @yashkumar,  
Thanks for providing this feedback on how we could improve the user experience! I've moved this post to our main [Troubleshooting custom flows](https://connective.celigo.com/c/6) section, and have let the PM in charge of mapping know about this issue.

---

<div class="post-metadata">

**Author:** ![scotthenderson](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/scotthenderson/32/6780_2.png) [@scotthenderson](https://connective.celigo.com/u/scotthenderson)\
**Post date:** [November 8, 2022, 8:51pm UTC](https://connective.celigo.com/t/advance-mapping-only-perform-mapping-when-checkbox-exception-case/614/3 "2022-11-08T20:51:12Z")

</div>

Yes, in theory every checkbox field should always be true or false. That said, there are systems/applications out there where a checkbox field can be undefined/empty/null until someone explicitly sets a value for it. One example is when you define a new checkbox field for an existing database schema where there is already a bunch of data/rows, and then the checkbox field will be empty for all the existing data/rows until you set a value for it via a separate update query. Another example is when you add a new custom checkbox field to an application like NetSuite (i.e. or any application where you can define custom fields), and then unless you run a mass update to set the field to an initial value, it might be empty for existing records.