-
In the ongoing saga of the dynamic links from document configuration, I have the script running correctly in the onClick, I have the dynamic data statically “bound”, but now the script that sets the sessionScope variable says that sessionScope is not defined. I thought this was a “page global” thing in the client?- Interesting. I thought wakka (#) meant client-side code, but in another custom control that uses sessionScope on JS with wakka, it says it’s server side when editing with the script editor via All Properties. But the link’s onClick is set to use client side, and it also has a wakka on it, and when I set that onClick to server side, it changed to a dollar ($). So it seems a wakka is being used to mean both server and client side. Unexpected.
-
The “server-side” wakka implies sessionScope is server-side only. Is it?
-
Thanks for your time…