Select to view content in your preferred language

Existing Feature Service as Ouput. Objectid Error

492
3
09-29-2022 11:29 AM
ArmstKP
Frequent Contributor

I have selected an existing feature service as an output in a big data analytic.  I get this error:  "Failed to find ObjectID from feature layer", even though I have an objectid field.  Any thoughts/ideas?

 

ArmstKP_0-1664476075599.png

 

0 Kudos
3 Replies
PeterNasuti
Esri Contributor

@ArmstKP Thanks for reaching out! I would like to investigate this on my end to see if there is a workaround or a way we can better handle this on the Velocity side. Two options:

  1. Are you able to share this layer in an ArcGIS Online group with my ArcGIS Online account, "pnasuti_iot"?
  2. Can you provide a screenshot of the "fields" section of this layer on the service layer REST endpoint?
    1. Fields.jpg
0 Kudos
ArmstKP
Frequent Contributor

@PeterNasuti I have shared two layers with you.  Two different versions of the same feature layer.  Here is the screenshot:

ArmstKP_0-1664479270008.png

 

0 Kudos
PeterNasuti
Esri Contributor

@ArmstKP Thanks for sharing this layer with me! I was able to reproduce the issue and can confirm it is due to the fact that your only present layer index for this service is 221, rather than the expected 0. I wrote an enhancement/bug on our side to enhance the product to lookup layer IDs dynamically for the Feature Layer (existing) output rather than assuming the first layer index is 0.

VelocityLayerIndex.jpg

In the meantime, I suggest the following workaround attempt:

  1. Create new item in your ArcGIS Online content referencing your layer URL including the sublayer index
    1. https://services6.arcgis.com/MU31z9HAakdc3W69/arcgis/rest/services/Velocity_ParkingLot_4326_2/Featur...
  2. Choose to store credentials with this item
  3. Proceed with setting your sharing/tags/information as desired
  4. Use this new item to reference in ArcGIS Velocity when configuring the Feature Layer (existing) output

Please let me know if you have success with this workflow