"fields" and "nestedFields" Parameter Not Applied to Account System Objects
Written By
Allison McGill
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- Using the GET Rest API for account-restricted objects does not seem to follow the `fields` and `nestedFields` parameters for the linked account. For example, when querying a custom object and attempting to fetch a specific field from the related account, the API returns the entire account object instead of just the specified field.
Resolution
- As of 2025.Q1, this is currently the expected behavior. As account objects are system objects, as opposed to custom objects, they do not have the same degree of flexibility as custom objects. These system objects cannot be modified due to the role they play in the core of the product itself. It is on the roadmap to be addressed in the future but not the short term.
Did this article resolve your issue ?