Dialog Widget Property “dialogOpened” Missing/Broken in OpenUI5 1.96

  • Deniz
    Participant
      1 month, 1 week ago #70752

      I am encountering a runtime error when using the standard Dialog widget in a module that was originally created with OpenUI5 1.71 and subsequently migrated to OpenUI5 1.96 by changing the System Library setting.
      When attempting to bind the dialogOpened property to true, the dialog fails to open. The application does not crash, but the following error is logged in the browser console:

      Uncaught Error: Property “dialogOpened” does not exist in Element “sap.ui.core.Control#…”

      Is there a way for me to make OpenUi5 1.96 widgets work in this module, or do I have to create a new module with version 1.96 right from the start?

      Kind regards
      Deniz

      Vitali Kurdasov
      Moderator
        1 month, 1 week ago #70756
        Up
        1
        Down
        ::

        Hi Deniz,

        in the current StandardContent there is a Ui5 Upgrade Wizard, which can update the library aswell as widgets used in your Applications and Modules. Can could try using that one to get all widgets to the current version.

        Kind regards,

        Vitali

         

        Attachments:
        You must be logged in to view attached files.
        Deniz
        Participant
          1 month ago #70760
          Up
          0
          Down
          ::

          Hi Vitali,

          thank you for the tip. Unfortunately it did not solve my problem.
          After running the upgrade wizard all the widgets in the module were on version 1.96. But now all the dialog widgets return this error when trying to bind to the ‘dialogOpened’ property:

          Property “dialogOpened” does not exist in Element…

          Kind regards
          Deniz

          Deniz
          Participant
            1 month ago #71045
            Up
            0
            Down
            ::

            Solved: The solution for me was to copy the module and delete the old one…

            Lukas Henninger
            Moderator
              Has successfully completed the online course Introduction
              Has successfully completed the online course Intermediate (200)
              Has successfully completed the online course Advanced (300)
              Has successfully completed the online course Basics (100)
              Has successfully completed the online course Advanced (310)
              Has successfully completed the online course Advanced (320)
            4 weeks, 1 day ago #71143
            Up
            1
            Down
            ::

            Hi Deniz,

            I’m glad it now works now. The solution puzzles me a bit.

            What values are set as BaseType and Type in the Dialog Widget? You can find this in the “Others” section when the widget is selected.
            How do you open the dialog? Is there a binding, or a mapping like in an UI-Action?

            Kind Regards
            Lukas

            Deniz
            Participant
              4 weeks, 1 day ago #71163
              Up
              0
              Down
              ::

              Hi Lukas,

              I open the dialog with a UI-Action mapping.
              BaseType: sap.m.Dialog , Type: io.simplifier.widgets.m.Dialog_1_96

              Kind regards

              Deniz

              Armin Winkler
              Moderator
                Has successfully completed the online course Introduction
                Has successfully completed the online course Intermediate (200)
                Has successfully completed the online course Advanced (300)
                Has successfully completed the online course Basics (100)
              3 weeks, 4 days ago #74749
              Up
              1
              Down
              ::

              Hi Deniz,

              thank you for your reply. The type of the widget seems to be fine and matches our standard content distribution. Also, opening the dialog via a UI action and mapping a constant boolean value on the property ‘dialogOpened’ is the recommended way, so your configuration should not have been of an issue. The error you received is probably caused by the property not getting registered in the OpenUI5 framework. However, since you’ve already deleted the erroneous module from your environment, we can unfortunately never be sure about the root cause of your problem reported here.

              Next time, please don’t hesitate to open a ticket in our support portal if you require an error analysis from our side. Based on a ticket, we can provide you with help much more efficiently and purposefully. I’m glad that you were able to resolve the issue on your own in the end and for updating this topic accordingly.

              Kind regards,

              Armin

            Viewing 7 posts - 1 through 7 (of 7 total)

            You must be logged in to reply to this topic.