Hi,
I would like to clarify a limitation I encountered when working with the Paycheck entity (Screen ID: PR302000 - Paychecks and Adjustments) via Web Services.
While reviewing the entity, I noticed the following warning on certain fields:
"Do not include fields of this object in a request that retrieves a list of entities. To retrieve those fields, request entities one by one by specifying key fields."
From my understanding, this means that some fields (such as detail-level fields like Taxes or similar sub-objects) cannot be retrieved using a standard list request and instead require querying each record individually using its key fields.
I would like to ask:
- Is there any supported way to retrieve these fields in a single list request (e.g., via
$expand, endpoint configuration, or other approaches)? - Are there any recommended alternatives to avoid multiple per-record API calls, especially for large datasets?
- Would using a Generic Inquiry (GI) or custom endpoint be the only viable workaround to retrieve these fields in bulk?
- Are there any performance guidelines or best practices when dealing with this type of scenario in Acumatica APIs?
Our goal is to efficiently retrieve Paycheck data along with its related detail fields without needing to perform multiple sequential requests.
Thank you for your guidance.
