Issue with multiple combo boxes on one page (MX 10.12.10)
0
Currently running into the following problem: We have a page which has 3 combo boxes on it as filters. Essentially the first value is used to filter the seconds pontions and so on. This means that we also hide the following combo box(es) until a value was selected. Resulting in the following sequence: Combo box 1 visible with no value - CB 2 invisible - CB 3 invisible. Combo box 1 visible with a value - CB 2 visible with no value - CB 3 invisible. Combo box 1 visible with a value - CB 2 visible with a value - CB 3 visible. Options for CB2 are reliant on the value of CB1, Options for CB3 are reliant on the values of CB1 & CB2 (using microflows) This works 99.9% of the time, but sometimes we get following error when selecting a value for CB2: An error occurred while executing microflow data source for widget MasterdataModule.ArticleRetailerSortingHelper_SortArticles.comboBox3: Cannot set properties of undefined (setting 'hash') Error: An error occurred while executing microflow data source for widget MasterdataModule.ArticleRetailerSortingHelper_SortArticles.comboBox3: Cannot set properties of undefined (setting 'hash') at Xe (http://localhost:8080/mxclientsystem/mxui/mxui.js?638737523341505077:61:207736) at http://localhost:8080/mxclientsystem/mxui/mxui.js?638737523341505077:61:221830 The error is not blocking, as after clicking it away the 3rd combo box has the correct and expected options, so it does load properly in the end. I've tried updating the widget to the latest version (Based on other forum posts I found for similar issues for other widgets) and I added extra checks on the datasource microflow for CB3 to check whetehr we actually have a value for CB2. Neither fixed the issue, it just seems to happen less. Any1 else that had this issue/got it fixed? (I had to select 10.12.9, as 10.12.10 was not an option for some reason.)
asked
Hubert Bullen
1 answers
0
Hi Hubert,
Looks like, the object s somehow getting deleted from the memory, please make sure, there's no activity which delete the object.
Because the activities are not able to find the object to change or do action on it, it throws error.