Script error

(3) Share

Report

Posted on by Daniel Hart

Hi,

in the events sectrion on dynamics we have had a script error pop up last week. nothing has been changed yet it now brings this up

Cannot read properties of undefined (reading 'getFormContext')Session Id: xxxEvent Name: onchangeFunction Name: EventMgmt.CrmWebResource.Handlers.eventAndSessionStartDateCheck_checkEventStartDateWeb Resource Name: msevtmgt_EventMgmt.CrmWebResourceSolution Name: MicrosoftDynamics_EventManagementPublisher Name: microsoftdynamics

any help here would be great

I have the same question (0)

All responses (6)

Answers (0)

LanceP1906 54 on at

Like (0)

Report

Script error

Is your start date set incorrectly?

Was this reply helpful? Yes No
Angge011101 3 on at

Like (0)

Report

Script error

Hi,

We also encountered this error upon loading the form. Does anyone have a fix for this?

Was this reply helpful? Yes No
Edgar@LCI 59 on at

Like (0)

Report

Script error

Yeah same problem we are having. Will open a ticket with MS.

Was this reply helpful? Yes No
Chris_SKIT 8 on at

Like (0)

Report

Script error

deleted

Was this reply helpful? Yes No
Chris_SKIT 8 on at

Like (1)

Report

Script error

Did you find the source of this issue? We also get it since a few weeks. When I debug that specific Microsoft web ressource I see that the executioncontext is indeed undefined so not passed for some rreason and that is very strange:

EDIT: we found the issue seems in our event form in our solution the Context was indeed not passed

no idea why probably noone from us removed it maybe the script changed and did not require it in earlier versions this is all a bit strange but at least we know how to solve it

Was this reply helpful? Yes No
Suggested answer

nerdifand on at

Like (0)

Report

Script error

we dont use the ootb form, which was updated correctly by the marketing solution alongside the webresource. the function probably was changed to use the formcontext and this change is not properly relfected on selfmade-entity-forms.

passing the execution context at this onload-function will get rid of the script error.

Was this reply helpful? Yes No