Latest Contributions by TylerSchwartz2

File geodatabase.  Yes, the featureclass within the domain file gdb is added and visible in the map (selecting it is how I am navigating to the data>domain ribbon/window). And to respond to your comment in the other thread, per my testing just now, closing the domain window works on the first time running "table to domain" GP tool (ie: for the first domain added), but running subsequent table to domain GP tools does not reveal the subsequent domains, even after closing and re-opening the domain window. So it appears to only work on the first domain added, but thats it. Still need to close out of Pro in order to get those subsequent domains to appear. ... View more

Hi Kory, this worked on the first table to domain I ran, but subsequent ones do not appear - even after closing and re-opening the domain window. Very strange. Hopefully this helps - Ill take further feedback to the other thread, thank you. ... View more

Thanks Kory for the quick and detailed response.  The first thing I tried was closing and reopening the domain dialog, the second thing was to remove and re-add the feature class to Pro.  As you noted, the only way to update was to close and re-open Pro.  I appreciate you looking into this and look forward to a fix. Thanks again ... View more

Just to clarify with a supporting screenshot.  You can see the tool ran correctly, but the domain does not show up unless you completely close out of Pro.  If I re-run the tool, I get an error saying the domain already exists. To me, this clear proof that Pro is not updating and is not seeing the new domain, which to me, is connected to this larger issue outlined in the thread. The only way to get the domain to appear is to close out of Pro, and reopen the project.  It doesnt seem efficient or logical to have to close out of your Pro project every time you need it to update. Clearly something is wrong here. ... View more

To add to the description of this behavior so we can get some resolution, I have another issue when adding domains to a geodatabase. When I run "Table to Domain" and add a domain to a geodatabase, these domains are not visible or able to be added to my subtypes unless I close out of pro and reopen.  This has to be done each and every time I add a domain using this GP tool.  A manual refresh on the geodatabase does not reveal these domains.  You must close out of Pro for them to be visible under the "Data>Domains" ribbon. Now surely, you cannot say this is expected behavior and surely this points to the larger issue that Pro seems to have on refreshing files, no? Kory Kramer‌ ... View more

This isnt our responsibility to collect data and test and quantify, its ESRI's.  Thats why we pay for the software, and I am 100% sure they have the data and they are aware of the issues affecting slower-than-ArcMap performance. ... View more

Just to be clear, I support and like Pro, overall.  I think it has a lot of great innovations and personally I like the UI in general.  My issues with Pro are purely on the development side - the bugs and the performance issues that are not being acknowledged or proactively caught and fixed by ESRI. The fact that its slower and less efficient than ArcMap in a variety of commonly executed tasks...  If they can get Pro to be as efficient as ArcMap and get the majority of the bugs (which they wont acknowledge are bugs) fixed, I will be 100% a fanboy of Pro.  Please do not confuse my critique of the issues with the fact that overall, I see immense potential with Pro.  It just needs to perform better. ... View more

Try scrolling through an attribute table and see how laggy and unresponsive it is.  There is a plethora of performance issues that Pro suffers from, but just scrolling through an attribute table is the most stark and easy to see.  Beyond just the performance issues, many other problems exist (signing in/out of accounts doesn't update Pro/AGO permissions/extensions, catalog file tree doesnt update/forced refresh needed, the list goes on).  Here we are over two years out of beta and we still have beta level issues persisting and not being patched or caught by development/qaqc team.  I was an early adopter, and because of that I have seen all the bugs and issues present from version 1.0 til now - many have been fixed (some of which I had to report)... whereas other, larger issues have not. Selecting polygons, performing edits, running a calculate field, ribbon/UI updates, spinning wheels.  These processes should have instantaneous responsiveness like they do in ArcMap, but they dont. These are the issues that users are complaining about, and they are not small issues!. This inefficiencies in Pro add up over the course of a day and causes frustration when the software cant move as fast as your mind.  This is accentuated because ArcMap DOES move that fast, so these issues are amplified. The feedback specific to Pro being less efficient than ArcMap on Geonet is widespread-- I do not accept that these are isolated issues and I believe ESRI knows about them but arent being forthcoming about it. I will freely admit I LIKE Pro and it DOES have a lot of great things going for it. .  I like the UI, I like the new map layout/legend, I like the added symbology and labelling options (transparency), but all of those things fall flat if it is much less efficient than ArcMap. We expect Pro to be as responsive (or more responsive) than ArcMap and we expect ESRI to QA/QC their product, not us. ESRI needs to get serious about the speed and efficiency issues that Pro currently has if they expect users to adopt Pro over the currently much more efficient ArcMap. Surely ESRI knows this but cant seem to achieve (or acknowledge) it, why? ... View more

The Add Subtype tool requires you have a table (feature class) that already has a subtype field designated.  This tool will add more code name pairs to the already setup subtype.  The "input table" listed in the tool is the already existing feature class that has the subtype already setup, unfortunately.  This tool is different than the "Table to Domain" tool. I do not know of a way to import a large list of subtypes in a table automatically, but as you mentioned this can easily be done with a domain. You may have to setup each subtype individually.  I have found this is much easier to do in Pro using the "Data" ribbon, "Subtypes" tab, and then clicking on the Create/Manage.  This will allow you to add multiple subtypes (albeit manually) without having to run the "Add Subtype" tool multiple times. ... View more

A couple ideas. 1) Is your default printer set in Windows correctly? 2) I usually never print out of ArcMap or Pro, better (for me) to export a PDF and print from there. ... View more

Editing in Pro is a total chore.  I have set a layer to be the only selectable layer, trying to merge two pieces of a polygon in that layer, keep getting the error "The destination layer type cannot be merged" - on top of that, selecting polygons, splitting polygons and most editing tools/clicks/processes are just slow, arduous and with a delay of a second or more.  This is in Pro 2.4.1.  This is not an issue with my local machine as this has persisted across multiple machines (my home computer and work computer). ESRI has a lot of work to do to get 64 bit Pro to be as quick and responsive as the 32 bit ArcMap... ... View more

Thanks for the clarification - makes sense! ... View more

Thanks Kory, thats very interesting. I did a bit of further testing on this and I am wondering if you are aware of the following: I can log into an account that has a standard license, log out and back in as a different user with basic license (but still retaining the Standard License and features).  Then, someone else in my organization logs into Pro with that same Standard license account and yet, we both have simultaneous access to a sole Standard license (tools extensions etc). This could potentially be repeated for as many accounts as needed by logging in with the Standard account and then logging out and back in with the Basic account. Maybe I am missing something here but to me that seems like quite a loophole wherein an organization or group of individuals could all simultaneously share a singular Advanced/Standard license and/or extensions?  Are you positive this is by design? ... View more