My understanding is that for the Location Referencing toolbar to appear in ArcGIS Pro 3.0.3 when using an Enterprise Geodatabase these requirements must be met:
In an existing project I have a map view open, and I can see the Location Referencing (and Linear Referencing) tab present (as expected).
Into that project I insert a New Map, and into that map I use Add Data to add a layerfile named Route Editing Layers (DEV Portal).lyrx. As expected, the Location Referencing (and Linear Referencing) tab appears, and I can see the expected network, centerline and calibration point features classes and that their sources are feature service feature classes. I close that project without saving because it was only a test to prove the layer file does what I think it should.
I restart ArcGIS Pro without a template, and insert a New Map into it. I use Add Data to add the same layerfile named Route Editing Layers (DEV Portal).lyrx into that map. This time, the Linear Referencing tab appears but not the Location Referencing tab, even though I can see the expected network, centerline and calibration point features classes and that their sources are feature service feature classes.
Why might the Location Referencing tab fail to appear in the second test?
If I create a new project using the Map Template, and add the same layerfile into its only map, then the Location Referencing tab fails to appear there too. I am confident that in the past the second and third tests would have produced the expected result and am at a loss as to why even with several laptop and ArcGIS Pro restarts this problem has emerged and remains.
@GraemeBrowning_Aurizon The pre-conditions stated are correct and once met the Location Referencing ribbon 'should' show. Also, look for the Location Referencing tools under Geoprocessing. If they show with a lock - the license is not available. If the GP tools show, perhaps it is the layer file. You can test by adding the feature services directly. Feel free to log a Tech Support incident if this abnormal behavior continues.
@AyanPalit Thank you for those ideas to try, which I did on a project created without a template and inserted a New Map into.
I've tried refreshing the portal from the Portals tab of the Project Page and that does not resolve it.
I think the issue must be with one or all of the three feature services.
Something we did recently was to try a variation to copying the LRS from our Production down to Development. In the past I've always deleted the Feature Layer and Map Image Layer before deleting the old DEV LRS and copy/pasting the PRD LRS, configuring Branch Versionings, and recreating both by using Share As Web Layer. This time a colleague using his own credentials used the same workflow but only stopped (instead of deleting) the Map Image Layer service and then restarted it at the end. When I can see the Location Referencing tab I have no problem editing using my own credentials so the only quirk seems to be that these feature services added to a New Map do not enable the Location Referencing toolbar, unless the project has an existing map in which they had already been enabled.
I've not yet logged a Tech Support incident because I'm only working at this site one day this week and one day next week. Unfortunately, other project demands mean that I won't have time to liaise with Tech Support on any testing that is exploratory rather than focused on what I've found so far.
The two ways that I know and think will allow me to workaround this problem are:
Another bit of software behaviour that seems odd is:
@GraemeBrowning_Aurizon The process followed to copy LRS between the 2 environments doesn't align with documented process. I tend to agree that the feature service seems to be missing a property, such that Pro cannot detect LRS.