Developer forum

Hi Scott,

The exception can be reproduced on DW9.10.8 as well. It occurs on first saving of already storred feed has query just selected regardless other options are selected or aren't. I've submitted new Bug 2293 to fix it.

Regarding issue with user control, I see it can be reproduced on your solution with users seem to have been exprorted only (under live integration), but not with ones created in regular way. Note the control has user Id instead of name on saving after selecting in the case. User selector cannot be performed after it at all until control is empty via 'cross' and resaving. Since, your solution is under live intgration, so we need to have extra look in the issue, comment will be provided later. Thanks.

BR, Oleg QA  

Hi,

I was not able to reproduce the issues related to using user in feed on my regular environment. Since it's issue of your specific solution, so submit case to support if relevant to have deep dig. Thanks

BR, Oleg QA 

Hi Oleg,

Nice find! I worked it further and found that it's due to having line breaks in the username. You're right that the backend wouldn't support that occurring, but integration does allow that strange but possible situation.

You can repro by updating the username of a user with something like this:

update AccessUser set AccessUserUserName = 'My Test User
 ' where accessuserid = xxxxxxx

Note the line break before the closing '.

We'll see if we can update the customer's data to remove the line breaks, but can you create a bug for this please to handle for line breaks (ASCII Characters 10+13 or either 10 or 13)?

Thanks,

Scott

Hi Scott,

New bug 2439 has been submitted to fix the issue (prevent line breaks in either integration or fix user control). Thanks for clarifying.

BR, Oleg QA 

I do not think this is a bug fix in our end.

You cannot even login using a line break. So the data has to be cleaned...

Thanks Oleg.

Nicolai, while it is bad data that we've asked the customer to clean up, it has been like that for about 5 years for over 5K users. These are customer accounts that are impersonated from seperate login accounts, so the username doesn't have a specific role except to display something unique. So we've been able to survive with the ugly data everywhere except for in the PIM feed.

Scott