Wj-flex-grid control property is undefined leading to some exception in 2018 v

Posted by: sivavenkatakoteswararao.kota on 3 January 2019, 2:57 am EST

    • Post Options:
    • Link

    Posted 3 January 2019, 2:57 am EST

    Hi Team,

    We have been planning to migrate to 5.20182.524 with Angularjs(1.7.3), but noticed our existing wj-flex-grid (was working with 5.20173.409) stopped working, after debugging noticed control property on the gird is undefined. Here is the sample Flex Grid:

    <wj-flex-grid items-source="ctrl.data"
                                      control="ctrl.control"
                                      selection-mode="CellRange"
                                      sorting-column="ctrl.sortingColumn(e)"
                                      beginning-edit="ctrl.beginCellEdit(e)"
                                      cell-edit-ended="ctrl.cellEditEnded(e)"
                                      resized-column="ctrl.resizedColumn(e)"
                                      resizing-column="ctrl.resizingColumn(e)"
                                      allow-dragging="0"
                                      item-formatter="ctrl.itemFormatter"
                                      auto-generate-columns="false">
    </wj-flex-grid>
    

    We also tried adding "initialize=“ctrl.intiGrid(s,e)”, in which we were setting ctrl.control = s, but, even, that did not help us.

    As part of migrating from 2017 version to 2018 version do we need to do any changes to the above grid. Thank you!

  • Posted 3 January 2019, 5:14 am EST

    In the console log we have been observing below error messages during this observation.

    *** Assertion failed in Wijmo: Invalid enum value. thrown

  • Posted 4 January 2019, 1:21 am EST

    Hi,

    We are sorry but we are unable to replicate the issue at our end. We prepared a sample based on the code snippet provided and everything seems to be working fine, also ctrl.control seems to be initialized properly.

    Could you please have a look at the following sample and let us know if are missing anything to replicate the issue: http://jsfiddle.net/exradupk/

    *** Assertion failed in Wijmo: Invalid enum value.

    <<<<<<<<<<<

    This error means that somewhere we are trying to assign a value to one of the properties of control which is not valid/not supported. Please make sure that only valid values are assigned to the control. As for the code-snippet, everything seems to be fine with it.

    ~Sharad

  • Posted 23 January 2019, 5:17 am EST

    Hi Sharad,

    Sorry for late reply, I was on vacation!

    We figured out the problem and fixed the issue. As you mentioned, we were trying to assign improper value to a property, corrected that now.

    Thank you!

    Br//Siva

  • Posted 24 January 2019, 12:18 am EST

    Hi,

    We are glad to hear that you were able to resolve the issue and thank you for notifying us about the same.

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels