07-18-2019, 03:42 PM
(This post was last modified: 07-18-2019, 04:17 PM by clarencemartin.)
I think that I have figured part of this out. I didn't understand about using the cdb_userTable to get the CDBUsersTable id. for the query.
the following script yields: only user recordID's
on mouseUp pButtonNumber
local tInputA, tOutputA, tUsers
put cdb_userTableName() into tUsers
put cdb_query("email","~","*.com",tUsers,"cloud","recordList") into tOutputA
answer tOutputA
end mouseUp
OK, I changed the "recordList" to "RecordData" and I see all of the Array data.
Jason,
creating a list of users will allow an Administrator to pick a user from a list that he/she wants to delete.
Deleting a user with the LCM is easy, but an administrator may want to delete a particular user via the application and having a list of users is the way to do this.
I am actually changing the following line in the script" to:
put cdb_query("email","~","*.*",tUsers,"cloud","recordList") into tOutputA.
the reason : there may be emails that are ".com", ".net" or any ".?" .
the following script yields: only user recordID's
on mouseUp pButtonNumber
local tInputA, tOutputA, tUsers
put cdb_userTableName() into tUsers
put cdb_query("email","~","*.com",tUsers,"cloud","recordList") into tOutputA
answer tOutputA
end mouseUp
OK, I changed the "recordList" to "RecordData" and I see all of the Array data.
Jason,
creating a list of users will allow an Administrator to pick a user from a list that he/she wants to delete.
Deleting a user with the LCM is easy, but an administrator may want to delete a particular user via the application and having a list of users is the way to do this.
I am actually changing the following line in the script" to:
put cdb_query("email","~","*.*",tUsers,"cloud","recordList") into tOutputA.
the reason : there may be emails that are ".com", ".net" or any ".?" .