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)
Thats right. There seems to be no propper way to get the User-Details from a User type Variable, App Info or Table Record.
Only the hardcoding of a User (in Expression editor or in the user select dropdown in the trigger) allows this (or a Placeholder on the Users Table).
This detailed selection should be available on User objects in the Trigger editor for variables, App Info and Table Records as well…
@Beth Is there a bet practice to display details from variable user types?
This behavior is expected based on how Tulip handles user context in triggers. The App Info Logged In User is treated as an active session user, so fields like Username and Name are more reliably available. Users coming from a table record placeholder or selected in the trigger editor are treated as data objects, and not all user attributes are consistently exposed or resolved in triggers. This is why storing the User type works, but some individual fields may return blank. Using TOTEXT(User) or storing needed values in custom user fields is currently the most reliable workaround.
Hi @nicolo.lagravinese , @thorsten.langner and @jmlowden ,
This might not be achievable directly using Tulip expressions or data manipulation triggers, but I implemented a similar use case earlier using a custom widget.
Here’s what I did:
You can check the implementation below for reference where user list is user variable and user detail is text variable.
This is the custom widget code i used. Only 3 lines of java script code. No Html and no css.
If anyone has a simpler workaround or alternative method, please feel free to share!
