Skip to main content
Solved

Request to OData DAC endpoints for the 'Length' field results in ECONNRESET

  • January 8, 2026
  • 3 replies
  • 30 views

I have a development instance of Acumatica 2025R2 setup and am testing sending requests to the OData DAC endpoints.

 

Specifically I am targeting the PX_Objects_CS_Segment endpoint and have noticed an issue when including the Length field in the $select parameter.

 

When testing in Postman, these requests return the expected data:

These requests result in ECONNRESET errors:

Is there something special about the Length field that the DAC endpoint is having an issue with? Or maybe there is something to do with how I deployed the development instance of Acumatica?

 

If I send similar requests (with the Length field in the $select parameter) to these DAC endpoints (all of which have Length fields in the metadata) a similar ECONNRESET error is returned:

  • PX_Objects_GL_FinPeriods_MasterFinPeriod
  • PX_Objects_CS_Dimension
  • PX_Objects_CS_CSBox
  • PX_Objects_GL_FinPeriods_OrganizationFinPeriod
  • PX_Objects_IN_INItemBoxEx
  • PX_Objects_SO_SOPackageDetail
  • PX_Objects_SO_SOPackageInfo

There are obvious workarounds for this if the issue is internal (ie: since I need the Length field in the returned results, I can just omit the $select parameter in the request), but if this is a local configuration issue and won’t be present at a live client, I want to solve it that way.

 

Thank you.

Best answer by Dmitrii Naumov

@Jamesb 

thanks for reporting. I sent it to engineering team to review and fix

3 replies

Forum|alt.badge.img+8
  • Captain II
  • January 8, 2026

It may be because Length is part of the OData specification it is being treated like the length function. I’m not sure how to encode fields that use reserved words but that might be how you can handle that.

The other way could be to create a non-persisted field called xlength that pulls it’s value from the Length column and is read-only. Then you can reference that new field in your request without causing the error.


Dmitrii Naumov
Acumatica Moderator
Forum|alt.badge.img+7
  • Acumatica Moderator
  • Answer
  • January 10, 2026

@Jamesb 

thanks for reporting. I sent it to engineering team to review and fix


  • Author
  • Freshman I
  • January 12, 2026

@Dmitrii Naumov Thank you!