I am noticing some differences in trigger behavior when trying to save user data to tables. There are inconsistencies between using a trigger acting on the attributes of the (1) app info current logged in user, vs. (2) a users table record placeholder or (3) a specific user selected in the trigger editor (including the User>Current Logged In User drop-down option).
- Not all Users Table fields visible in the CSV exports (both “standard” and “custom fields” CSV exports from the Users Table) are exposed for data manipulation triggers, e.g. “Badge ID”
- Table Field: User
I am able to use a trigger to write the User data type for a user to tables data for all three scenarios - Table Field: User Text 1
I am able to use a trigger to write the UserName data only for the current logged in user (“Username”), not for a trigger-drop-down specified user (“User Name”), nor for a users table record placeholder user (“User Name”) - for the (“User Name”) I can specify in the trigger but there is no result in the table - Table Field: User Text 3
I am able to use a trigger to write the User’s Name for the current logged in user (“Name”) and a trigger-drop-down specified user (“Name”), but not able to specify this in a trigger for a users table record placeholder user - Table Field: User Text 3
Casting TOTEXT(user) works for all three scenarios
Top= (1) app info current logged in user
Middle = (2) a users table record placeholder
Bottom = a specific user selected in the trigger editor (including the User>Current Logged In User drop-down option)






