Has anyone encounter the same error? Appreciate any input on how to resolve this error. Thank you so much.

That's an issue with the drag and drop module by the looks of that message. Generally anything prefixed "dad" relates to that.

Hi Neil, thanks for answering, really appreciate it. May I know what should be the initial steps that I should do to resolve this issue? Thank you

It's not possible to say 100% what's happening and to resolve it but it looks like it's trying to get user preferences looking at the screen shot (getUserPreference). Maybe as s starting point, if there's any preferences you know that it's expecting, make sure they are filled in / selected? If you still cannot resolve it after that you'd need to take it up with whoever owns the drag and drop bundle as it may be a bug. It's a NetSuite provided bundle isn't it?

I am not sure as this error was encounter by some of our users with the same role when entering bill. I tried replicating the same steps on my end using the same role but I'm not encountering the error. So far there are only 3 users affected and all users have the same subsidiary and NetSuite role.

Yes but does the drag and drop addon expect the user to have certain preferences set up? (USER not ROLE)

Sorry, quite new to NetSuite, how do I check for this? Thank you

I'm not a user / admin / consultant I'm a developer so nothing I really do day to day but I would imagine if you hover over home (little house icon top left) and then choose "Set Preferences" You might find options in there for drag and drop. At this point I'm guessing, as I don't have drag and drop in an account I have access to to confirm. If there are no preferences to be set I'd suggest raising a support case.

Thank you so much Neil really appreciate your responses! I checked both the bundle installed and Set Preferences. For bundle update is available. I will update the bundle and check the Set Preferences of the affected users. Again thank you so much!

Were you able to resolve this? We are having this exact same problem. @Mavis

Has anyone try using incognito and avoid the issue?