If you can verify that adding the user causes the history to come through, that would make sense. The OOTB solution has ALL users in the enterprise, and users which only operate in the field have a special "ALWAYS MOBILE" role assigned. While its unfrortunate that they don't have a 'defualt user' or a way to recover this history, it makes a certain amount of sense because they store the user name as a record in the history row.
Thanks for the info, I didn't really pay attention to that 'always mobile' role. ArcFM Desktop Configuration Guide .
We have a large amount of field users and of course we have employee turnover so keeping the enterprise session manager and field session manager
up to date with proper users and roles is challenging - but possibly keeping the enterprise session manager db up to date and then exporting the users to
import into the field session manager may work. I still think it may be beneficial to show the history even if the user doesn't exist in the db.
Hello, Jim! It looks like the correct answer may have been provided for this question. If so, please click the Correct Answer button on that reply. If this question is still unanswered, please let us know so we can continue to pursue the answer. Feel free to provide any further detail that may help those in the community respond appropriately. Thank you.