REST Api operation queryEditLog missing from LRServer

746
7
09-19-2023 11:44 AM
AlisonWieckowicz
New Contributor III

We are using a Roads and Highways 10.7.1 with Event Editor and ArcGIS Enterprise 10.9.1 Server with location services enabled.   There doesn't appear to be a rest endpoint for queryEditLog.   I have perused the rest catalog pages and I don’t see this operation anywhere.  Using a rest URL that mirrors the documentation without ArcGIS Enterprise DNS returns 400 “Invalid URL”.

Event Editor uses the same root LRS_Server rest endpoint and seems to work fine.   I have confirmed that the database account that is used to publish the network dataset has access to the data and we followed the documentation LRS access privileges here: https://desktop.arcgis.com/en/arcmap/latest/extensions/roads-and-highways/access-privileges-in-the-l...

Are we missing something?  Does the lrs_edit_log table need to be added to the map document used to publish the location enabled services?

For more info see here:

https://developers.arcgis.com/rest/services-reference/enterprise/lr-query-edit-log.htm

Here is an example of the rest catalog page with the operation listed from ESRI lrs sample server:

https://lrssample.esri.com/server/rest/services/RoadsHighways/NewYorkRoads/MapServer/exts/LRServer

Equivalent URL with out server return 400 “Invalid URL”  :

https://<our server dns>/lrsfed1/rest/services/otsm/EE_op/MapServer/exts/LRSServer/queryEditLog

Tags (2)
0 Kudos
7 Replies
AmitHazra
Esri Contributor

Hello - Can you confirm you are trying to leverage an ArcMap 10.7.1 published service with an ArcGIS Enterprise GIS Server 10.9.1 licensed with Location Referencing Solutions for Server? If you are, this is an unsupported configuration. Once you migrate ArcGIS Enterprise to 10.9.1 you will need to upgrade your LRS GDB to our ArcGIS Pro-based model and republish services using ArcGIS Pro. 

Please reference our migration resource document:
https://community.esri.com/t5/arcgis-roads-and-highways-questions/migrating-from-arcmap-to-pro-3-1/m...

-amit@esri  | Esri Transportation LRS Team

AlisonWieckowicz
New Contributor III

Thank you this is helpful.   I think I failed to provide the correct versions or at least enough detail.   

GDB with ALRS - 10.7.1 

ArcGIS Desktop Publishing Client - 10.7.1

Federated LRSServer -  10.7.1

Enterprise Portal - 10.9.1 for event viewer authentication.

Is this a supported version configuration?  How do we know what version combinations are supported for Roads and Highways?

0 Kudos
NathanEasley
Esri Regular Contributor

We would recommend keeping all parts of the Enterprise (Server, Portal, etc.) at the same version to avoid the types of issues it sounds like you're encountering with a mixed environment.  As you transition to Pro in the future, you'll need to keep your Pro and Enterprise versions in alignment https://enterprise.arcgis.com/en/roads-highways/latest/get-started/esri-roads-and-highways-for-serve...

NathanEasley
Esri Regular Contributor

The queryEditLog endpoint only exists for the version of the REST API that comes with services published from Pro.  You can easily tell the difference by looking at the URL for LRSServer vs LRServer.  LRSServer is for ArcMap published services and LRServer is for Pro published services.

Nathan
Roads and Highways Product team

AlisonWieckowicz
New Contributor III

Ok.  So we must publish with ArcGIS Pro to make use of queryEditLog function of the REST API.  Our business is not ready to begin editing the ALRS using pro.  Would it be sufficient to publish a second LRServer using ArcPro and an account that has read only access to the ALRS and LRS_EDIT_LOG?

Are there any other options for reviewing the edit log at 10.7.1 using an automated process?    ArcPy?    

Thank you for all the help,

Ali

0 Kudos
NathanEasley
Esri Regular Contributor

The Edit Log is a table within the gdb that has your LRS.  You can query it the same way you would a regular gdb table.  The information about the edit does live in an XML blob so you would need to be able to convert that XML into something readable.

The only warning with this approach is to make sure you don't add/update/delete any of the records in the table.  Treat it as read only to see route edits that have occurred within the LRS.

AlisonWieckowicz
New Contributor III

Ok.  Thanks.   I am aware of the table but was trying to avoid using XQuery.   I will give that a try.

Thanks,

Ali

0 Kudos