Dear Community,
Did anyone else experience any issues with nesting two or more custom build composite components in SAP Build Apps recently? Platform: web deployment.
So some more explanation:
In SAP Build Apps, developers can create custom components with internal logic, private variables, and properties. These components can also trigger events and expose data to their parent components. Previously, it was possible to nest custom components without issues: events triggered by a nested component would propagate correctly, and private variables within each component would remain isolated.
Issue Overview:
Since a recent update (runtime: 4.12.132), this behavior has changed. Now, when a nested custom component triggers an event to its root custom component, the root component’s private variables are unexpectedly reset. This disrupts the internal logic, leading to inconsistencies in functionality and data handling.
Is this a bug, or is it an intentional change in behavior that we should adjust our implementations for? Any insights or plans for addressing this would be highly appreciated!
We have realised that avoiding nested custom components and relying on ‘primitive’ components within one custom components seems to resolve the issue, however, it seems to not be the best way of doing component-based UI. There was no such issue on the previous runtime that we built our web app on: 4.12.127.
Looking forward to your insight.
PS for visual people just a simple graphic:
