Latest Contributions by KoryKramer

I suppose that would be part of the documentation piece needed here.  I'll make sure to get this to the team that will be updating the documentation. ... View more

I suppose that would be part of the documentation piece needed here.  I'll make sure to get this to the team that will be updating the documentation. ... View more

As stated in that other idea, the explanation from development about this functionality is "SIMILAR TO has been implemented in the File Geodatabase. It is a SQL standard implementation that provides access to Regular Expressions. Using Regular Expressions on like is not part of the SQL standard, even though many RDBMS systems have chosen to add support. With File Geodatabase SQL we follow the SQL standard wherever possible." Would you be able to use Similar To? ... View more

As stated in that other idea, the explanation from development about this functionality is "SIMILAR TO has been implemented in the File Geodatabase. It is a SQL standard implementation that provides access to Regular Expressions. Using Regular Expressions on like is not part of the SQL standard, even though many RDBMS systems have chosen to add support. With File Geodatabase SQL we follow the SQL standard wherever possible." Would you be able to use Similar To? ... View more

[ENH-000110409 Provide documentation for supported SQL pattern matching] is marked as In Product Plan.   Like Joshua stated,  ENH-000110699, Esri updated the status to "Not In Current Product Plan," The explanation provided with that status update was "SIMILAR TO has been implemented in the File Geodatabase. It is a SQL standard implementation that provides access to Regular Expressions. Using Regular Expressions on like is not part of the SQL standard, even though many RDBMS systems have chosen to add support. With File Geodatabase SQL we follow the SQL standard wherever possible."  Hopefully that helps those who are interested in this functionality. As for the status of this idea, well, since it asks for expanded pattern matching and it looks like that is is not in the current product plan, and also asks for documentation, which is in the product plan, we'll just leave this at reviewed and when we get the documentation this will be partially implemented. ... View more

[ENH-000110409 Provide documentation for supported SQL pattern matching] is marked as In Product Plan.   Like Joshua stated,  ENH-000110699, Esri updated the status to "Not In Current Product Plan," The explanation provided with that status update was "SIMILAR TO has been implemented in the File Geodatabase. It is a SQL standard implementation that provides access to Regular Expressions. Using Regular Expressions on like is not part of the SQL standard, even though many RDBMS systems have chosen to add support. With File Geodatabase SQL we follow the SQL standard wherever possible."  Hopefully that helps those who are interested in this functionality. As for the status of this idea, well, since it asks for expanded pattern matching and it looks like that is is not in the current product plan, and also asks for documentation, which is in the product plan, we'll just leave this at reviewed and when we get the documentation this will be partially implemented. ... View more

Thanks for reporting this, Thomas.  Yes, it appears that it happens when a subtype is applied to the feature class.  I have logged the following bug: BUG-000112731: With a subtype applied to a feature class, when the feature class is symbolized on a field with a domain applied, symbol labels are repeated. This bug will now go to the development team to be addressed. Thanks again for reporting this to us. ... View more

Thanks, Joe.  I think it would be best to log a case with technical support as this is going to take some specific troubleshooting on that data/database.  Thanks. ... View more

OK, if I followed the flow and screenshots there (and thank you a million times over for screenshots, as things like this are nearly impossible to follow without them ) it does look like you have records in your data that actually contain the text "<Null>" .  Where did the data come from to populate that database? If that is the case, do a new selection to select all records with an actual text value = "<Null>" Then Calculate Field field_name = None    (by default, the Expression Type should be Python 3, no quotes around None should give you actual null values in the cells of the selected records). Run the Select by Attributes again to check. Does that work? ... View more

Thanks for the additional context! ... View more

Thanks for the additional context! ... View more

Joe, I realize you said local portal, but as a quick test I tried this with a hosted feature service on ArcGIS Online and the selections appear to be working as expected: I think this one is definitely worth a call to technical support.  Things we'd probably want to dig deeper on are 1. are you referencing data on your own enterprise gdb - what is the RDBMS? 2. If you run the selection on the local data (same database used to generate the service) what are the results? ... View more

You could give that blue some transparency by clicking its dropdown arrow > Color Properties to open the Color Editor and setting transparency: Maybe that will help. ... View more

Not that this would be a 1:1 solve for creating multiple ring buffers with the buffer wizard, but for the use case of creating faded edges, you could look into using the gradient fill option in ArcGIS Pro. Fill symbol layers—ArcGIS Pro | ArcGIS Desktop  ... View more