Is your feature request related to a problem? Please describe.
In some cases (e.g. non LDS supported objects such as Task and Event, complex data management including callouts),
it may be necessary to display cards without going through the Lightning Data Service.
Describe the solution you'd like
Currently, only a Use DML? property has been implemented to execute some special updates in "without sharing" DML
modes for some Experience Cloud usages.
The idea would be to generalize this feature and offer a way to fetch / update data directly via SOQL/DML (e.g. for Task
or Event objects) or Apex (to include callouts to external systems).
Describe alternatives you've considered
In order to avoid reimplementing the lightning-input-field base components, an option would be to systematically
leverage "proxy" SObjects and lightning-record-edit-form in creation mode to display/interact with record data.
The form load / submission would be then overriden with custom logic.
To support non LDS Sobjects, a simple field mapping would be required (SOQL and DML being automatically used).
To support custom logic, custom Apex classes implementing a generic virtual class would be also used.
Additional context
This would be quite similar to the solution used for data fetch in sfpegListCmp and dmlForm action types in
sfpegActionBarCmp.
Is your feature request related to a problem? Please describe. In some cases (e.g. non LDS supported objects such as Task and Event, complex data management including callouts), it may be necessary to display cards without going through the Lightning Data Service.
Describe the solution you'd like Currently, only a Use DML? property has been implemented to execute some special updates in "without sharing" DML modes for some Experience Cloud usages. The idea would be to generalize this feature and offer a way to fetch / update data directly via SOQL/DML (e.g. for Task or Event objects) or Apex (to include callouts to external systems).
Describe alternatives you've considered In order to avoid reimplementing the lightning-input-field base components, an option would be to systematically leverage "proxy" SObjects and lightning-record-edit-form in creation mode to display/interact with record data. The form load / submission would be then overriden with custom logic.
Additional context This would be quite similar to the solution used for data fetch in sfpegListCmp and dmlForm action types in sfpegActionBarCmp.