Verify places does not seem to work per instructions
Verify places has been difficult at times. One thing is that when I look at the details for a person and return to verify places screen, the screen is frozen. This has happened every time I have done this lately. I would like to be able to delete and enter correct data when no choice fits.
Answers
-
There have been several reports in recent days. I think the first was here, on April 22. Two other posts have been made in the last day or so.
This particular issue seems to be a fault that has been occurring for months at random times, and may separate from the series of faults that has been going on for the last week. I had been thinking about posting for a while. This is just one excerpt from a list of faults in the Verify Faults activity that I have been compiling.
Random occurrence: Cannot click in the Standardized Place textbox and cannot select a Standardized Place from the list
Sometimes, in the middle of a batch, it will decide not to respond to clicking the Standardized Places textbox unless I click right at the end of the text. At the same time, it also may not allow me to select a standardized place from the list. This makes it pointless to continue the batch.
This is a long-standing issue.
It does seem that this was sometimes occurring when I switched from one browser tab to another and back again, but that was not always the case. On occasion, it would happen as soon as I started a batch, or in the middle of normal progression through a batch.
For the benefit of the engineers, I have noticed the following in this scenario. If there are several standardized places to choose from, I may be able to "select" one of the lower ones on the list. I just can't "select" one of the first couple of entries on the list, which may or may not be the one I want. I say "select" in quote marks, because, when I do click on one of the lower entries, the text that gets transferred into the Standardized Places text box may be different from the name of the place that I clicked!
0 -
I have experienced this as well. For some reason, it loads slowly on Edge and Chrome but on Firefox it works fine. FYI, there was a browser update for both Edge and Chrome a few days ago and I did Verify Names a few days ago on Edge and it worked fine but when I updated my browser today, that was when the issues started.
0 -
Verify Places has all kinds of issues 1) if you open a separate tab to look at a map VP won't work when you click on its tab again 2) you cannot tweak non-standard info to give a standardized place 3) you can't leave VP to go to another Opp like Full Name Review, instead you need to sign out of FS then sign in again … the list goes on … I think the system is unable to handle the number of users —-
0 -
I have just discovered that when Verify Places is running (and theoretically idling) on Windows, it is continually sending and receiving network data at about 2 megabits/sec. So, my advice is not to even go near Verify Places until this is sorted out.
I've also tried the activity on my Android phone, using the Chrome browser. I behaves just as badly there.
2 -
It looks like the new Chromium update may have broken something cause Firefox works fine. Explains why Edge isn't working since it uses the same browser engine as Chrome.
2 -
And that network data activity has me thinking "broken script" that continually asks for something from either the client or server, but never understands the answer, so asks again and again, much like a kid that asks "But Why?" without really wanting to know why.
4 -
I can confirm that Windows Firefox doesn't have the problem with the screen freezing (the original problem raised by @JoanneUdy1). I have also tried the Samsung Internet browser on my Android phone. The problem occurs there. That browser is Chromium-based too. All my Chromium-based browsers (Chrome, Edge and Samsung Internet) have been updated in the last few days. This certainly points a finger at Chromium.
The issue that I raised on April 27, and was referred to as item #2 by @maryellenstevensbarnes1 appears to be a separate problem. This relates to not being able to edit the text or select an item in the list. It has been going on for some months now. It also occurs in Windows Firefox, so it doesn't seem to be Chromium-based. Maybe it needs a discussion of its own.
1 -
@maryellenstevensbarnes1, I have found a sort of workaround for the problem of not being able to edit the standardized place or select an item from the list.
When the activity gets into the ornery state, try clicking the Standardized Place textbox or the list item further to the right than you might naturally do. Anywhere in the right half of the controls seems to work. As you move the mouse pointer to the right, it should change from its default up-left-pointing arrow to an insertion indicator or a hand with a pointing finger. When you click there, you should be able to edit the text or select an item.
It seems like the code is miscalculating the horizontal position of the controls relative to the current mouse pointer position. The problem with the list appears to apply only to the first two or three items in the list. The lower entries (if there are any) are usually selectable but Sod's Law would suggest that you would more frequently want to select one of the items at the top of the list. There is apparently a problem with the calculation of the vertical positioning of the controls as well.
Now that the other problem with Chromium-based browsers seems to have been fixed, I have been able to test this workaround in those browsers as well as in Firefox.
1
