Just a couple of items to be aware of when you're working with Dialog 2, Action Scripting and Data Binding.
The videos for Dialog Component - Managing Data in the Security Framework, D_SF_x, are great in detailing what's going on. Here are two additional notes. This deals mainly with accessing and editing Registered User and Security Framework info.
1. I thought I could CREATE my "RegisteredUsers" table using the tools in Data Binding. However, because you're essentially dealing with two separate tables (Security and User Info) you can't do this. You must first create the "RegisteredUsers" table (or whatever you want to call it) and then use it as described in the videos. If you attempt to create the table using the Data Binding tools, the "RegisteredUsers" table is selected for all the Security fields as well... which doesn't work out too well.
2. ExecuteServerSideAction Action Scripts are available, and work, for the Server Side Events. However, they are available BUT do not seem to work for Xbasic functions... as in an Ajax Callback. The workaround here is to add the Action Script, then choose the option in the Action Scripting menu to convert the script to code. For some scripts, like the "Populate Dialog from Tables" script, the code creates javascript to be passed back into the client. You must assign this javascript to the name of your Xbasic function so that the code will get returned. E.g. At the end of the "Populate Dialog from Tables" converted code...
And now, pass this javascript back to the client. My XBasic function is named "getRegUsersInfo"
The videos for Dialog Component - Managing Data in the Security Framework, D_SF_x, are great in detailing what's going on. Here are two additional notes. This deals mainly with accessing and editing Registered User and Security Framework info.
1. I thought I could CREATE my "RegisteredUsers" table using the tools in Data Binding. However, because you're essentially dealing with two separate tables (Security and User Info) you can't do this. You must first create the "RegisteredUsers" table (or whatever you want to call it) and then use it as described in the videos. If you attempt to create the table using the Data Binding tools, the "RegisteredUsers" table is selected for all the Security fields as well... which doesn't work out too well.
2. ExecuteServerSideAction Action Scripts are available, and work, for the Server Side Events. However, they are available BUT do not seem to work for Xbasic functions... as in an Ajax Callback. The workaround here is to add the Action Script, then choose the option in the Action Scripting menu to convert the script to code. For some scripts, like the "Populate Dialog from Tables" script, the code creates javascript to be passed back into the client. You must assign this javascript to the name of your Xbasic function so that the code will get returned. E.g. At the end of the "Populate Dialog from Tables" converted code...
Code:
dim e.javascript as c = default "" e.javascript = e.javascript + crlf()+\ jsPopulateControls + crlf()+\ jsErrorMessage + crlf()+\ jsDebuggingMessages
Code:
getRegUsersInfo = e.javascript
Comment