Thanks for the feedback, Vladimir Stojanovic. It's nice to see that there are a couple of things that you like about ArcGIS Pro:) The team that works on Attribute Table functionality in ArcGIS Pro reviewed your feedback and they shared some suggestions that might help in certain cases. Some of what you mention they already have as issues to work on, and at least one thing will be in the next release.
1. “Still not possible to zoom to ALL selected rows."
or using this button:
To zoom to all selected rows across many layers using the Map tab > Navigation group:
2. “There is an icon right bellow (), indicating whether table is sorted or not. This is quite unnecessary for me, because you cannot do anything with it."
The team does have an open issue to make that icon clickable. It's good to know that that would be helpful for you!
3. “Generally, it seems there are a couple of very odd effects related to work with new search field (ctrl- F). The thing is, they are not so good reproducible, often almost hidden. First off, it is not always obvious which column is being searched. The text “Find in: <name of column>” is not always visible.”
The only time this should happen is if the table view is very narrow. Are you seeing something different?
4. “In addition, there is possibility of different behavior depending on whether is any row in table selected or not. Not quite sure about this one. Since I am a great fan of work with keyboard, after many tries I came up with following workflow, which turned out to have minimum odd behavior and other errors.
- First click on column header (it determines which column is the search by and AFAIK the only way is by mouse)”
Using the arrow or tab keys in the table should update the field name:
5. “- Then click in the field to give criteria (string to be searched for)
- Click enter button. Now happens following:
- Sometimes is all fine, first row with found text jumps in front of your eyes
- Otherwise, sometime a row is found, but it doesn’t jump to be visible. In this case I click enter button once again and voila, lazy table jumps to first row with wanted text.”
It may depend on where the table has focus the first time you hit Enter. In the following clip, all 58 records contain the word 'Park' so searching for 'pa' returns all 58. Continuing to hit Enter should not change anything.
To move through the found records, one would use the arrows in the Find and Replace UI, or the keyboard arrow keys. Note below (using a different dataset) that moving through the attribute table with the keyboard does not update the Find and Replace UI. Is that what you're describing?
6. “The odd part is, in second case, when it finds something, but doesn’t jump to that row, you haven’t got possibility to “kick it” to jump. Nice would be for example, to empower the arrows for jumping through the list of found rows () to do exactly that- jump to that only row found. These arrows are disabled when just one row is found (which seems to be logical, since there is only one row found and there is no need for scrolling through results). I am not sure I described it clear enough though."
I think I see what you're saying. Does F3 not work for you?
7. “One thing more. It appears that ctrl-F jumps on result only when the result is in the same screen, means you do not have to scroll to the result. Simply put, if the result row is here somewhere on the screen, it will be highlighted. If not, system doesn’t jump forward or backward on it. Then, when you klick again on search button, then it does jump to result. This appears to be reproducible, it repeats every time again."
We're not seeing this. It's possible that we're just not understanding the steps. If you're able to provide steps to reproduce (does it have anything to do with the data being used?), it could be looked at. Here is what I see when searching for a record that is not already showing on the screen:
8. “There is though a way to improve this unfortunate ctrl-F tool. Not sure how costly for programmer would it be. Instead of always having to click on column header to set attribute you are searching by, there should be a drop- down menu with all attributes from table direct beside other buttons of ctrl-F, on the right side..."
How many fields are in the tables that you typically work with? Having a dropdown for hundreds of fields would be cumbersome. The design does allow you to search on all fields though:
9. “I miss those arrows from ArcMap to navigate through table . Especially when I want to jump to the end of table (or begin for that matter). Yes, I could use combination Ctrl- Arrow, but it is not always convenient.”
Move to End/Beginning of table will be in Pro 2.6!
10. “Load all is very, very annoying, to say the least. It appears as developers opinion, a table with 2000 or more entries is too much for modern computers memory to handle. Come on! Two thousand rows..."
The team has taken this feedback. Thank you.
11. “Scrolling through the table is very laborious..."
Scrolling in tables is definitely a known issue and the team is looking at improving this in the future. For now, it is possible to configure what you see when scrolling through the layer's Display settings:
As seen when scrolling:
12. “And then, this Go to row number navigation. How in the world should I know the number of any row? I mean, the first ten I could counter down, but further? Wandering where can I read the row number. No clue.”
This was an ArcMap equivalency issue https://community.esri.com/ideas/14999 You can read other user's opinions about the functionality on that thread.
For the comment about Calculate Field taking a long time, are you able to share the project package where you notice this, along with the steps that demonstrate the lag (i.e. calculate x field, using this expression... etc.)? If you're able to, the geoprocessing team could take a look.
Thank you for your balanced feedback. I hope that providing some specific responses are helpful to your work!