Managing Data from External Systems
Liferay Objects provides low-code capabilities for modeling data structures and implementing business logic integrated with Liferay DXP. Using this framework, you can create user experiences with custom workflows, validations, notifications, and more.
Proxy objects were initially released as a beta feature. The feature flag was changed from beta to release in Liferay DXP 2025.Q2/Portal GA135.
By default, object definitions create tables in Liferay’s database for storing entry data. However, you can configure your object to function as a proxy, using it to store and retrieve data from an external data source, like Salesforce.
Liferay’s tools for low-code frontend applications that display and managing objects data can be used to create applications for externally hosted proxy objects: add new data with form containers, list existing entries in collections, and provide individual entry detail pages with display page templates.
Rather than duplicating and syncing data between systems, the proxy storage type uses a single data source outside Liferay. This can help reduce data inconsistencies and conflicts between systems. Alternative approaches to this problem can involve costly and complex custom solutions. By using proxy objects, you can leverage Liferay’s low-code features to more easily provide consistent user experiences while streamlining touch points and simplifying data management.
In proxy objects, fields are mapped to existing columns in an external system’s database, so data operations directly create or update the asset in the external system. For example, when users create an object entry, Liferay performs a POST request to the external system API endpoints and adds the data to that system’s database.
Proxy Object Limitations
Since proxy object data does not persist in Liferay’s database, some limitations are placed on proxy objects:
-
You cannot add field validations.
-
You cannot add object relationships.
-
You cannot index the proxy object data through Liferay.
-
There is no request queue or retry mechanism. If the attempted connection fails, any request not yet executed fails.
-
There is no caching. Every time an object entry is accessed, Liferay creates an HTTP request.
Besides these limitations, proxy objects share the same platform integrations as standard objects. See Understanding Object Integrations for more information.
Interacting with Proxy Object Data in Liferay
Like standard object definitions, you can use proxy object data in Liferay DXP to create dynamic user experiences. Once defined, you can access and display proxy object data using Liferay’s page builder features, client extensions, and more.
Examples include creating display pages for object data, displaying data in collection displays, and mapping entry values to fragment elements.
Supported Connectors for Proxy Objects
Liferay includes connectors to Salesforce and SugarCRM for proxy objects. With these, you can integrate your proxy object with Salesforce or SugarCRM objects. In this way you can use the external system for storage.
To use proxy objects, enable the Proxy Object (LPS-135430) feature flag and see Using Objects with Salesforce for more information.