We recently upgraded to version 2.25.0 and have discovered a new issue.
STEPS TO REPRODUCE
Open any screen with accordions/drop downs
Click away from the List screen with another link on the screen
Click the back button in the browser
ACTUAL RESULTS
Getting an error after hitting the back button: “OSUI-GEN-07002: There is already a Accordion Item under Id: 'l1-1278_29-$b24' added to Accordion with uniqueId: 0.jrgpaz04vz.”
It appears that this error was attempted to be fixed in version 2.24.0
Hi @Rebecca Hall
Given that it was some changes to those custom factory customizations, it's quite normal that you'll have unexpected behaviours since there's a situation where the full lifecycle of the components is not completed.Given that, I would suggest removing that option, understanding why someone set it, and fixing that issue instead.
Best Regards,GM
First of all, thank you for reaching out.
The task you mentioned was only for AnimatedLabel, so not relevant.
Could you please share a sample oml where this can be reproducible? This way, it's more efficient for the community to make sure we're looking at the same scenario.
Hi,
That error message —
OSUI-GEN-07002: There is already an Accordion Item under Id: 'l1-1278_29-$b24' added to Accordion with uniqueId: 0.jrgpaz04vz.
Is specific to OutSystems UI (OSUI), and it indicates a duplicate widget registration inside an Accordion component.
When you navigate back to a screen (e.g., via the browser’s Back button), OutSystems sometimes reuses existing UI components that haven’t been fully destroyed.In your case, the Accordion component (from OSUI) is trying to re-initialize itself, but an Accordion Item with the same internal ID (l1-1278_29-$b24) already exists in the DOM.
Updating to the latest OutSystems UI (OSUI) version often fixes lifecycle and navigation bugs.
If possible could you please share your oml file ?
I think you're right about the screen lifecycle, it doesn't quite get removed when going to an external link. Our administrator found this setting in Factory Configuration. When we turned it off the errors went away. I'm not sure if not having the Ready event running affects other screen functionality or not.
Hi @Gonçalo Martins
Does this mean that new settings in the factory configuration are not generally checked for compatibility with other products supported by OutSystems? If so, it would be helpful to document this at the appropriate places.
Is there an overview of which Factory Configuration settings OutSystems UI is tested with or compatible with?
Thanks and best regards
Magnus
It looks like a similar issue was happening with mobile previously: https://www.outsystems.com/forums/discussion/82115/outsystems-ui-tabs-error-when-returning-to-previous-screen-in-mobile/
I'm attaching a sample module in addition to the logs files from the console.
I'm a bit confused here.
In your initial post, you mentioned accordions/dropdown; the error displayed is about the Dropdown Server Side Item, and in the OML you shared, I can't see either of them, only Tabs.
Could you please clarify and detail all the use cases (or even better, add them to the OML)?
Cheers,GM
After more testing yesterday, we're realizing it's tabs or accordions are affecting applications. I think since we were getting javascript errors for drop downs included since the other components weren't working. When clicking on a link to an external site, and then using the browser back button causes widgets to throw javascript errors that prevents the screen from being usable.
I attached an updated oml with flows including working and broken screens.