• State Not Answered
  • Replies 17 replies
  • Subscribers 5 subscribers
  • Views 4392 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Reports

I am retrieving usernames into a multivalue text variable but I can't get them to display properly

smcgill

I am retrieving usernames into a multivalue text variable in an existing 6.6 app to be shown on a portal report but I can't get them to display properly.
Some of the rows on the report are from older versions of the pm but the set up of the variables is same, the only difference is that the older versions were populated from a DB using a lowercase function which has been removed for the new ones.
When the report column is set to the user name format I can see the older rows formatted as a name eg Adam Smith, but new rows don't show at all.
If I switch to User or Group Name or the group profile format I see values for all rows but they are shown as the user name and not formatted eg smitha.
I'm not sure why the older data is being treated differently as the code seems to be the same.
Is there any way to convert the pv to display all rows with formatted names?
I have tried various functions but I'm obviously missing the correct combination and if an...

OriginalPostID-121436

  Discussion posts and replies are publicly visible

Parents
  • 0
    Appian Employee
    Can you attach a screenshot showing the behavior? I am not clear on how the "old" values differ from the "new" in the report.

    Based on what I read I am thinking there are still usernames which do not map existing users and since the columns are evaluated in expression groups the InvalidUserException they may be triggering is impacting the other variables (You can confirm this by filtering to show only a specific username you know that exists and matches the characters exactly as in the People tab to see if it's the rest of the data impacting the valid users)
Reply
  • 0
    Appian Employee
    Can you attach a screenshot showing the behavior? I am not clear on how the "old" values differ from the "new" in the report.

    Based on what I read I am thinking there are still usernames which do not map existing users and since the columns are evaluated in expression groups the InvalidUserException they may be triggering is impacting the other variables (You can confirm this by filtering to show only a specific username you know that exists and matches the characters exactly as in the People tab to see if it's the rest of the data impacting the valid users)
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.