-
Notifications
You must be signed in to change notification settings - Fork 211
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Big issue in Master Detail screen #28
Comments
Thank you
…On Mon, May 9, 2022, 6:42 AM cargomarprojects ***@***.***> wrote:
[image: apex_error]
<https://user-images.githubusercontent.com/45616767/167347463-41e673a0-6097-4152-86cd-29917d70c06b.png>
—
Reply to this email directly, view it on GitHub
<#28 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AW45QPKKYAUFEHI4G4CXB43VJCQU5ANCNFSM5VNDOYYA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue is with all master/detail screens created using oracle apex.
run the master detail screen and do the below steps to see the error.
We did lot of research on this and now we are asking our customers not to click any other master row when detail row is loading. is that the correct way of doing it ?
Pls find below the error shown in the browser console screen
interactiveGrid.min.js?v=22.1.0:6 Uncaught TypeError: Cannot read properties of null (reading 'serverOffset')
at q... (interactiveGrid.min.js?v=22.1.0:6:16443)
at P (interactiveGrid.min.js?v=22.1.0:1:1128)
at Object.forEachInPage (interactiveGrid.min.js?v=22.1.0:1:17452)
at Object.next (interactiveGrid.min.js?v=22.1.0:1:16854)
at Object._drainWaiters (interactiveGrid.min.js?v=22.1.0:1:33703)
at interactiveGrid.min.js?v=22.1.0:1:8607
at c (desktop_all.min.js?v=22.1.0:2:28327)
at Object.fireWith [as resolveWith] (desktop_all.min.js?v=22.1.0:2:29072)
at Object.s. [as resolve] (desktop_all.min.js?v=22.1.0:2:30973)
at interactiveGrid.min.js?v=22.1.0:1:8474
The text was updated successfully, but these errors were encountered: