Field sets versus custom action overrides for count and adjustment screens
Key Takeaway
Field sets control which custom fields appear on inventory count and adjustment screens, while custom action overrides control which Lightning component opens for New, Edit, or View. So a custom field for the adjustment screen goes in the Adjustment header field set on the Inventory Operation object.
Sample Inventory Management in Life Sciences Cloud gives you two separate tools for customizing its inventory count and inventory operation screens, such as the adjustment screen. Field sets control which custom fields appear on those screens. Custom action overrides replace the standard New, Edit, and View buttons with Life Sciences Lightning components. To choose between them, ask whether the requirement is about what a screen shows or about which screen opens.
Field sets versus custom action overrides
Both tools customize the same inventory count and inventory operation screens, but each one answers a different kind of requirement. The two tools also need different access.
If the requirement is to show extra business data, such as a custom reason or reference field, on an inventory count or adjustment...
Use a field set. Editing field sets requires the "Customize Application" permission.
If the requirement is about which screen opens when a user clicks New, Edit, or View on an inventory record...
Use a custom action override. Overriding inventory buttons requires the "Life Sciences Commercial Admin" permission set.
A sales operations team sends their admin two requests. The first asks for a custom Closet Location field on audited inventory counts. The second asks that the New button on inventory counts open a Life Sciences Lightning component. The first request is about what appears on a screen, so the admin uses a field set. The second request is about which screen opens, so the admin uses a custom action override.