Hi team, We are experiencing a minor issue with a generic interface that contains standard action buttons (Cancel, OK). This interface is called from two different Record Views: Record Summary 1 and Record Summary 2. Each summary has its own main interface which, in turn, calls our generic component. The Issue: Record Summary 1: Clicking the buttons works as expected. Record Summary 2: Clicking the buttons triggers an unexpected scroll to the top of the page. Observations: Interface Designer: When testing directly within the Summary interfaces, everything works correctly. Environment: The issue only occurs when accessing the views via a Record Link within a Site. Data Source Difference: There is one key difference between the Record Types: The working Record (Summary 1) points directly to a database table. The failing Record (Summary 2) points to a Data Store Entity (DSE). Can anyone helps?

Question

Technical Support Request: Inconsistent Scrolling Behavior in Generic Interface

Forum|Forum|6 months ago
January 14, 2026
4 replies
0 views

Hi team,

We are experiencing a minor issue with a generic interface that contains standard action buttons (Cancel, OK). This interface is called from two different Record Views: Record Summary 1 and Record Summary 2. Each summary has its own main interface which, in turn, calls our generic component.

The Issue:

Record Summary 1: Clicking the buttons works as expected.
Record Summary 2: Clicking the buttons triggers an unexpected scroll to the top of the page.

Observations:

Interface Designer: When testing directly within the Summary interfaces, everything works correctly.
Environment: The issue only occurs when accessing the views via a Record Link within a Site.
Data Source Difference: There is one key difference between the Record Types:
- The working Record (Summary 1) points directly to a database table.
- The failing Record (Summary 2) points to a Data Store Entity (DSE).

Can anyone helps?

harshas2775

Do you happen to have any form fields at the top of record summary 2? Also, after buttons are triggered what is the design afterwards - is it also identical?

C

codyv994620

The only thing that comes to mind when when scrolling to the top of the page is on a!formLayout the parameter focusOnFirstInput is default to true, maybe for this case, you would need to set it to false?

(Older versions of a!formLayout would be skipAutoFocus=True)

Hard to tell out seeing the interface.