Different Record Page for View / Edit - (No Visualforce)

You can combine action overrides with record types to achieve this effect. The action override simply calls the edit page with the new record type selected. A trigger or automation changes the record type back to the view mode when saving. Alternatively, on the detail page, you could just create a component to show the fields, while leaving the edit page alone. Note that any of these approaches have limitations anyways. It likely won't feel as good as the native UI. What you're asking for isn't a configuration-only feature.

What I have used as a workaround is the creation of a checkbox field that hides sections of the Record Page. In my case, when creating a Case record from the New button, I want only to certain fields to be displayed.

I place these fields in a specific section that is visible when the checkbox field is set to False (initial value). When I enter the record, I can show the rest of the sections by activating the checkbox (which also controls the visibility of those sections).

If we want to automate the activation of the checkbox, it could also be done by adding an RTF that changes the value of the field when the record is created...

While this approach is not the cleanest from a design perspective, it can serve as a pragmatic workaround in cases where avoiding Visualforce or custom components is preferred.

Unlike the solution proposed by Daniel, we don't need to create any additional fields. Instead, we can take advantage of existing fields on the object and use the visibility filters in Dynamic Forms to conditionally show or hide fields.

Approach

Let’s say we want to hide certain fields during record creation, but display them after the record has been saved.

We can configure field visibility conditions based on existing fields that meet the following criteria:

• creatable = false
• defaultedOnCreate = true

You can identify such fields using tools like Salesforce Inspector Reloaded. Here’s an example on the Case object:

These properties ensure that the field has a value only after the record is created, allowing the visibility condition to behave as intended: hidden on create, shown on edit/view.

For the Case object, you can use the CreatedBy field. More precisely, a field on the related User record, since CreatedBy is a lookup. The field chosen must also meet another requirement:

• nillable = false

This ensures that the visibility condition evaluates consistently. A good candidate is the Username field on the User object.

References

• API Field Properties