[Anonymous]

Hi Hunar,

  Did you try to use different users?

From what you say it looks like the people picker resolves a user and breaks it in 2 users.

Do you see any js error?

[Anonymous]

Hi ,

Yes that's what it does – breaks it in 2 users.

We did try to use different users. The issue persists with every username we have tested.

Cannot really see any js errors there.

Hunar

[Anonymous]

Hi Hunar,

  What happens if the user's name is only one word (ie "user"). How this name will be broken down?

Are those users coming from AD or are SP users?

[Anonymous]

Hey ,

If the user's name is only one word then the people picker resolves it as valid or invalid as it would normally do with a name.

Users are coming from AD.

Hunar

[Anonymous]

While filtering the records by a peron field on one of our dashboards, the name gets split into two separate names.

The scenario is as below:-

     • We go to dashboard and filter by a person field

     • Follow any one of the links to the view request page

     • Close and return to the dashboard

At this point the dashboard shows no records. On checking the filter, the name in the peron field has been split into two names with an error message – “You are only allowed to enter one item”. This causes no records to display.

This happens with all person fields being used in the filter.

For instance:-

The name is – Quest Web Parts

The people picker initially correctly resolves it as – Parts, Quest Web;

But on returning to the dashboard after having viewed the request page the name has been split and looks like this – Parts; Quest Web;

Is there any workaround for this?

We are using Quest Version 5.7

[Anonymous]

Hi Hunar,

  If the user is one word everything works as expected right?

Have you tries to check the ULS log file when the user name has 2 word in it? Any SP error/warning?

[Author]

Posts