Skip to main content
Question

Support for nested expands/translations

  • December 3, 2025
  • 5 replies
  • 46 views

Freddy
Forum|alt.badge.img+16
  • Thinkwise Local Partner Brasil

I don't seem to be able to expand more than 1 level. Is this correct and is there a way to go and extra level. Like I'm selecting via oData invoice, then expand into invoice_line and in the line I want to translate tag_id to get the name. 

5 replies

Forum|alt.badge.img+4

Hello ​@Freddy,

No, this is not correct, this is actually supported. Does my answer here provide enough insight?


Freddy
Forum|alt.badge.img+16
  • Author
  • Thinkwise Local Partner Brasil
  • December 3, 2025

Hello ​@Freddy,

No, this is not correct, this is actually supported. Does my answer here provide enough insight?

Can you give me an example of a odata call? I wasn’t able to get it to work. Let me try first by replacing transl- with lookup_..  to be able to get 2 levels. I’ll let you know


Nick Janssen
Moderator
Forum|alt.badge.img+5
  • Moderator
  • December 12, 2025

Hi Freddy,

Were you able to make some progress on this topic?
If the answer of Vincent helped you, could you mark it as best answer?

Best regards,
Nick Janssen


Freddy
Forum|alt.badge.img+16
  • Author
  • Thinkwise Local Partner Brasil
  • December 12, 2025

Hello ​@Freddy,

No, this is not correct, this is actually supported. Does my answer here provide enough insight?

I don't the nested level to show anything..  I cannot follow 

sf/43/charge(e15a01cc-e8dd-4350-934b-a256fffb4f9b)?$select=charge_id&$expand=detail_ref_charge_charge_line($select=charge_line,payment_id;$expand=lookup_payment_id),lookup_charge_counterpart($select=entity_type,address_id;$expand=lookup_address_id)

gives the following.  Both address_id as payment_id have a lookup defined in the SF. Inside the lookup_charge_counterpart.. it's not even showing the lookup_address_id ..  and the lookup_payment_id (or transl_payment_id) shows but stays empty..  whilst there is an id. 

{
"charge_id": "e15a01cc-e8dd-4350-934b-a256fffb4f9b",
"lookup_charge_counterpart": {
"entity_type": 2,
"address_id": 36
},
"detail_ref_charge_charge_line": [
{
"charge_line": 1,
"payment_id": 11638,
"lookup_payment_id": {}
}
]
}

 


Freddy
Forum|alt.badge.img+16
  • Author
  • Thinkwise Local Partner Brasil
  • December 12, 2025

Hello ​@Freddy,

No, this is not correct, this is actually supported. Does my answer here provide enough insight?

I don't the nested level to show anything..  I cannot follow 

sf/43/charge(e15a01cc-e8dd-4350-934b-a256fffb4f9b)?$select=charge_id&$expand=detail_ref_charge_charge_line($select=charge_line,payment_id;$expand=lookup_payment_id),lookup_charge_counterpart($select=entity_type,address_id;$expand=lookup_address_id)

gives the following.  Both address_id as payment_id have a lookup defined in the SF. Inside the lookup_charge_counterpart.. it's not even showing the lookup_address_id ..  and the lookup_payment_id (or transl_payment_id) shows but stays empty..  whilst there is an id. 

{
"charge_id": "e15a01cc-e8dd-4350-934b-a256fffb4f9b",
"lookup_charge_counterpart": {
"entity_type": 2,
"address_id": 36
},
"detail_ref_charge_charge_line": [
{
"charge_line": 1,
"payment_id": 11638,
"lookup_payment_id": {}
}
]
}

 

@Vincent Doppenberg lookup_payment_id is like this because apparently due to a lookup variant. When I remove it it shows data.  Why is this?