By using this website, you agree to our Terms of Use (click here)
If you need to print the Username of the person who ran an ARM (Analytical Report Manager) financial report writer report, you can use the following formula:
=Report.GetDefUI('AccessInfo.DisplayName')
I recommend putting it in the Column Set header and right justifying it like this:
So it prints on the report like this:
Someone is deep into developing financial reports this week.
Very useful tip. I can see adding it to a report footer to document who and when the report is produced.
Haha, naw, I just finally got around to knocking out some of the items that have been on my list for a while. Still a lot more on my list that I haven't been able to get to yet.
Regarding report page footer, that would be awesome if there was a way to do that. Do you know of a way? As far as I can tell, you can only do a report page header.
Nope. Guilty of "assuming facts not in evidence". Since you could do something like that in FRx, I thought something similar would exist in ARM.
Having said that, the header might work.
Ah, ya, in my experience so far, ARM is definitely not as comprehensive as FRx was. Also, Report Designer is not as comprehensive as Crystal Reports.
Have you tried this?
=Report.GetDefUI('RowAccessInfo.Username')
Tim,
Thanks for the reply. When I use 'Username', I get the same results as 'DisplayName' (the full email address). On a whim, I decided to try other potential fields based on the Inspect Element on the user screens but all of them resulted in an error that prevented the entire string from displaying. I tried FullName, LastName and AcctName (again with no results).
Is there a resource that documents all of the objects that can be used in the ARM reports? I have looked in the training guides, user guides and googled Report.GetDefUI to see if I could find any documents to no avail. I am reusing items that I have found in other reports but it would be nice to have a complete list. Thanks again.
Not that I know of, but that would be a great resource. I have been resorting to hunt-and-peck as well.
You might try an Acumatica support case to see what they say.
Thanks Tim