Question

Cannot read property ownerDocument of null

0

I am getting the following error on multiple buttons: An error occurred while executing On click at Linegenix.Location_NewEdit.actionButton2: Cannot read property 'ownerDocument' of null Error: An error occurred while executing On click at Linegenix.Location_NewEdit.actionButton2: Cannot read property 'ownerDocument' of null at http://localhost:8080/mxclientsystem/mxui/mxui.js?637205748175179279:73:274289 at we (http://localhost:8080/mxclientsystem/mxui/mxui.js?637205748175179279:35:9233) at r (http://localhost:8080/mxclientsystem/mxui/mxui.js?637205748175179279:35:9129) at m (http://localhost:8080/mxclientsystem/mxui/mxui.js?637205748175179279:40:134839) Wondering whether it has something to do with the repetitive following warning that I don’t understand: DEPRECATED: mendix.lang.nullExec. Use plain javascript if instead -- will be removed in version: 9.0 How may I troubleshoot those?

asked 2020-03-23

Patrick Prasquier

5 answers

Jesper Peterse · Answer 1 · 2020-03-23

The page doesn't receive an object. Perhaps because of access rights or because there is no object passed to the page. Check the access rights for the user, and try to open the page from a microflow and see if there is an object passed to the page?

Ronald Catersels · Answer 2 · 2020-03-25

Could it be that you are somewhere using the system member Owner somewhere in your model? And could it be that you set this member on a later stage and thus have records where the owner is not set and records where the owner is set?

Regards,

Ronald

Patrick Prasquier · Answer 3 · 2020-03-26

I assume it came from one of the record’s calculated fields that included calls to Java’s GetGUID and GetApplicationURL. Changing it to stored with the appropriate event handler (figuring out the right combination of after/before commit and steps’ commit value was tricky though) seems to have solved it.

Patrick Prasquier · Answer 4 · 2020-05-06

It seemed to have come from a QR code widget in responsive mode. Removing the responsive option and placing it into a container made the error disappear.

Jelte Lagendijk · Answer 5 · 2020-07-30

Revisited this old widget I created 4 years ago as there as a Support ticket regarding this widget. Although Community Support, I took a look at the issue and Patrick seems right, it was in the responsive mode. I fixed the issue in version 1.1.0