How to prevent auto-fill in Service Portal in Chrome?

[Community Alums]

In Service Portal, we have Chrome Auto-Fill blocking out ServiceNow choices for many users.  I've seen some community posts about blocking auto-fill passwords, mostly in native and some even suggesting DOM Manipulation, which I know is not a good idea.  Has anyone come across this issue and solved it?

Thanks!

[Elijah Aromola · Accepted solution]

Take a look at this community blog that goes over this.

https://community.servicenow.com/community?id=community_blog&sys_id=0fcca265dbd0dbc01dcaf3231f9619b3

[Community Alums]

Thanks for the quick response Elijah.  I actually read that post immediately before posting my follow-up question.  It was insightful, but doesn't seem to solve my issue.  I've listed some specifics below.  

1. The article (and KB referenced at the end) teaches how to move a password field immediately after a unique field to prevent an association to matching previous field,thus preventing auto-population.  Since it is not a password, moving the field doesn't break any association.

2. I believe we could ask all users to turn off auto-complete in the browser rather than configure the instance, but that doesn't seem user-friendly.  I'm really hoping to make the fix on the instance rather than ask users to make that change.

3. I'm working in Portal rather than Native.  

Any help would be greatly appreciated!

[lana5]

Did you get this sorted?  We have a similar request. TIA

[Community Alums]

Yes, did you check out Elijah's link?  There is a lot of info there, and it helped me solve this.