# Return value of maapi\_exists

**URL:** <https://dmap-community.ductus.global/t/return-value-of-maapi-exists/3301>\
**Category:** Core Engine and APIs\
**Created:** [September 24, 2020, 9:55am UTC](https://dmap-community.ductus.global/t/return-value-of-maapi-exists/3301 "2020-09-24T09:55:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Saswat](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/saswat/32/291_2.png) [@Saswat](https://dmap-community.ductus.global/u/Saswat)\
**Post date:** [September 24, 2020, 9:55am UTC](https://dmap-community.ductus.global/t/return-value-of-maapi-exists/3301/1 "2020-09-24T09:55:42Z")

</div>

I am seeing a discrepancy in return value of `maapi_exists` between confD 6.4.4 and confD 7.2.2.

For a set but uncommitted path, maapi\_exists returns 0 in confD 6.4.4 and returns 1 in confD 7.2.2. Here, maapi\_exists is invoked as part of a validation routine from the yang model.  
Because of this, the C application is failing return value checks.

Please suggest.

---

<div class="post-metadata">

**Author:** ![josephm](https://avatars.discourse-cdn.com/v4/letter/j/a88e57/32.png) [@josephm](https://dmap-community.ductus.global/u/josephm)\
**Post date:** [September 24, 2020, 11:01am UTC](https://dmap-community.ductus.global/t/return-value-of-maapi-exists/3301/2 "2020-09-24T11:01:35Z")

</div>

well, there may have been some fix related to `maapi_exists()` in between the versions.

if you think newer version behaves incorrectly for some specific check, you can add some brief YANG /request example for problematic YANG construct…

`maapi_` calls work on pending transaction, so your described case of return value 1 should be correct one…