search

GuidoPreite / DOSM

Dependent Option Set Manager
MIT License
5 stars 0 forks source link

facing error after upgrading to Wave 2 #8

Closed MuhammadMoiez closed 2 years ago

MuhammadMoiez commented 2 years ago

TypeError: Cannot read properties of undefined (reading 'forEach') at DOSM.FilterField (https://qa-X.crm4.dynamics.com/%7b637980194590000158%7d/webresources/gp_/js/dosm_DependentOptionSet.js:246:32) at y._executeFunctionInternal (https://qa-X.crm4.dynamics.com/uclient/scripts/app.js?v=1.4.4645-2208.2:2041:5286) at y.execute (https://qa-X.crm4.dynamics.com/uclient/scripts/app.js?v=1.4.4645-2208.2:2041:3782) at https://qa-X.crm4.dynamics.com/uclient/scripts/app.js?v=1.4.4645-2208.2:156:26702 at i (https://qa-X.crm4.dynamics.com/uclient/scripts/app.js?v=1.4.4645-2208.2:332:88) at ee._executeIndividualEvent (https://qa-X.crm4.dynamics.com/uclient/scripts/app.js?v=1.4.4645-2208.2:156:26676) at ee._executeEventHandler (https://qa-X.crm4.dynamics.com/uclient/scripts/app.js?v=1.4.4645-2208.2:156:23681) at Object.execute (https://qa-X.crm4.dynamics.com/uclient/scripts/app.js?v=1.4.4645-2208.2:156:23109) at N._executeSyncAction (https://qa-X.crm4.dynamics.com/uclient/scripts/app.js?v=1.4.4645-2208.2:946:692) at N._executeSync (https://qa-X.crm4.dynamics.com/uclient/scripts/app.js?v=1.4.4645-2208.2:946:419)

Error Details: Event Name: onchange Function Name: DOSM.FilterField Web Resource Name: gp_/js/dosm_DependentOptionSet.js Solution Name: DependentOptionSetManager Publisher Name: guidopreite

GuidoPreite commented 2 years ago

can you provide more details? the script was working before the update? or you installed in a Wave2 environment? can you write the exact version number of your instance? I will modify your post to remove the url of your instance

MuhammadMoiez commented 2 years ago

Hi, Yes it was working fine for last 1.5 years and last week we installed Wave2 and it started throwing this error. we are using this Dependent Option Set Manager 1.0.0.3 version

GuidoPreite commented 2 years ago

Right now I don't have an instance with Wave2 installed but tomorrow I will spin a trial. According to your log probably there is a problem retrieving the JSON configuration. I will update this issue as soon I have news. Thanks for reporting it.

GuidoPreite commented 2 years ago

Hi, I activated a new trial with Wave1, I installed DOSM and configured two dependent optionsets. After I upgraded the trial to Wave2 and the dependent optionsets are still working, so I am not able to replicate your issue. My suggestion is to try to configure a new dependent optionset inside your instance and see if also the new configuration is working or not. Please let me know of your test results. Thanks. (Screenshot of my server version) image

MuhammadMoiez commented 2 years ago

@GuidoPreite I had to regenerate the config file and it is working fine now. we faced this issue in all our 4 environments. But now it is working after regenerating. Thank you for taking prompt action

GuidoPreite commented 2 years ago

Thanks for the feedback, I close this issue as it is resolved.