The info is there for user name and email, but all my forms are pulling the submitter info as domain/username and it's causing any email tasks to suspend. Figured at first it was a sync issue but I've confirmed the users profiles in Laserfiche directory server have all the required info. Have found some users that work fine and a lot more that do not.
Question
Question
{/_useremail} Not pulling info from Laserfiche Directory Server
Replies
{/_useremail} pulls the current user's email address. If the field is visible, or the data is set up to be saved when the field is hidden, then it would pull the submitter's information.
If you're wanting to get around that and have it pull the email address for a user in a later process step/stage, I would recommend setting it up accordingly using field rules.
Here are a couple options:
Let me know if you have any questions and I can try to explain a bit more.
So it used to pull their email (by used to I mean Friday before the network team rebooted all the servers) but not it just pulls them as domain/username for most users. The info is there in the LFDS profiles, it's just not pulling it now and causing issues with forms that have been submitted.
{/_useremail} is the token for current user email and it should always show the current configured user email.
However for submitter email the related tokens are {/dataset/_initiator_email}, {/dataset/_submitter_email} and {/dataset/_fs_submitter_email}. These tokens would show user email cached when user submited the form.
For the expected token value of {/_useremail}, you may check db table [cf_users] and see the [email] column value for the user. If the email data are still empty, that means Forms still could not sync data from LFDS.
For the expected token value of submitter email, you may check db table [cf_user_snapshot]. Since the email should be empty when they submitted the form, you could modify this db to overwrite the cached data.