# Get-elem Callback not getting hit post get-next call for a inner level list

**URL:** <https://dmap-community.ductus.global/t/get-elem-callback-not-getting-hit-post-get-next-call-for-a-inner-level-list/3486>\
**Category:** CDB and CDB API\
**Created:** [January 29, 2021, 9:43am UTC](https://dmap-community.ductus.global/t/get-elem-callback-not-getting-hit-post-get-next-call-for-a-inner-level-list/3486 "2021-01-29T09:43:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Haripriya](https://avatars.discourse-cdn.com/v4/letter/h/3d9bf3/32.png) [@Haripriya](https://dmap-community.ductus.global/u/Haripriya)\
**Post date:** [January 29, 2021, 9:43am UTC](https://dmap-community.ductus.global/t/get-elem-callback-not-getting-hit-post-get-next-call-for-a-inner-level-list/3486/1 "2021-01-29T09:43:05Z")

</div>

Hi,

I have yang structure with the container and nested list.

```
 +--ro du
    +--ro RmaDU* [du-id]
       +--ro du-id int32
	   .....
       +--ro rim
          +--ro RmaRIM* [rim-id]
             +--ro rim-id uint16
             +--ro hwinfo
             | +--ro serial-number?   

```

The issue is, I do get all the callbacks as expected upto  
TRACE CALL data get\_next(thandle=40647, /RmaENB/du/RmaDU, -1)

I do set the key and was expecting the get-elem callback to be triggered (just the way I get in case of the 1st/outer level list).

```
        CONFD_SET_INT16(value, rim_id);
        next_key = 1;
        confd_data_reply_next_key(tctx, value, 1, (long)next_key);

```

However, I don’t get the get-elem callback for (serial-number) node.

Note: I do get --\> CONFD\_OK in the trace log for the reply next.

Am I missing something here?

Thank you in advance.

---

<div class="post-metadata">

**Author:** ![Haripriya](https://avatars.discourse-cdn.com/v4/letter/h/3d9bf3/32.png) [@Haripriya](https://dmap-community.ductus.global/u/Haripriya)\
**Post date:** [February 1, 2021, 5:37am UTC](https://dmap-community.ductus.global/t/get-elem-callback-not-getting-hit-post-get-next-call-for-a-inner-level-list/3486/2 "2021-02-01T05:37:02Z")

</div>

Hi,

I could get what was the issue (Need to use CONFD\_SET\_UINT16 )  
It’s working fine now.

Thanks.

---

<div class="post-metadata">

**Author:** ![mvf](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/mvf/32/182_2.png) [@mvf](https://dmap-community.ductus.global/u/mvf)\
**Post date:** [February 3, 2021, 7:29am UTC](https://dmap-community.ductus.global/t/get-elem-callback-not-getting-hit-post-get-next-call-for-a-inner-level-list/3486/3 "2021-02-03T07:29:20Z")

</div>

The callback trace you post here,

```
TRACE CALL data get_next(thandle=40647, /RmaENB/du/RmaDU, -1)

```

tries to address the list `RmaDU`, but your code, if that is what is responsible for the reply, responds with a value for `rim_id`, which is a key of the list `RmaRIM`. The important difference is that the two leaves have different type, `int32` for `du-id` and `uint16` for `rim-id`; so confd would get a value with unexpected type and refuses to continue further. If this is the case, you should see a complaint in this sense in devel.log.