I created a new point FC and imported a lyrx file for the symbology. The data fields are the same as when the lyrx field was created, but there are additional values in the field that "unique values" is using to symbolize. I'm choosing to "maintain ranges" so I can leave the other values in the "all other values" section.
Unfortunately, when I go to more>all other values, I am greeted with a yellow warning "Requested operation could not be completed". There's no error message and no explanation.
Am I going about this wrong, or is this a bug?
If I chose to update the ranges in the import symbology screen, incorrect symbols are applied to values that weren't in the original LYRX file. I would think that unmatched symbols would display as a generic point symbol. This behavior is the reason I'm choosing to "maintain ranges" so these other values are symbolized by the generic point symbol.
As a test, try bringing in old dataset that you used to create the .lyrx. Also bring in the new dataset you want to import the symbology to. With both layer in the project, click on import symbology but instead of choosing the .lyrx file to import, choose the old existing defined layer. See if that works.
Yes, the techniques you described have also worked for me in the past on previous versions of AGP. I've used both of them to import symbology into a new FC. The problem has appeared in 2.9.0.
I've included a screenshot of the error. All is shown is the yellow error message. There's no code or anything else more descriptive.
I'm also getting it when going into the new "Clusters" tab in the symbology properties, but I'm not even trying to make changes here.
Is this happening with other data you are working with or in other projects? As a test, can you create a new .lyrx layer and see if it will allow you to import it using import symbology?
Also, just an FYI... I found this thread from 1-25-2019 and this same issue appears to be logged as a bug at ArcGIS Pro 2.3.2, a fix was release at 2.5 and then it popped up again at 2.6.1 and beyond. Seems like ESRI hasn't kept an eye on this particular bug in their new releases? Here is the thread link if you want to read it:
Also, not sure if you know, but there is a BUG report site that ESRI publishes, you might want to do a search there to see if anybody has logged it and what the update is. If the test I mentioned in my post right before this one doesn't work and there isn't a bug reported, I would contact ESRI support and see if what they say.
Here is a link to the BUG report site: https://support.esri.com/en/Search-Results#search?q=arcgis-pro&content-type=Bugs