Select to view content in your preferred language

Error while parsing FeatureSet PBF payload

752
7
01-22-2025 11:09 AM
MKa
by
Frequent Contributor

name: 'query:parsing-pbf', details: {…}, message: 'Error while parsing FeatureSet PBF payload'

I have a simple Experience Builder app that I inherited but it seems to have an issue after I recently upgraded my Feature Services using the ArcGIS Pro Runtime.  After upgrading using the Pro Runtime, it get the following errors when I use the Search widget or I click on a table item to select/zoom to a polygon?  My map just goes empty.  My map works and is populated before i do the search.  And when i use postman the URL works and returns both PBF and Json. 

I see that my feature services now support PBF and my app seems to have problems parsing PBF.  I am currently on ArcGIS Server 10.9.1 and we upgraded our Feature Services using the ArcGIS Pro Runtime.  This worked before we did the upgrade, but we have to upgrade and we don't have a choice to use the old Arc Map.  I need to figure out what is happening.  

name: 'query:parsing-pbf', details: {…}, message: 'Error while parsing FeatureSet PBF payload'

"Error: Invalid data type!\n at f.skip (https://js.arcgis.com/4.23/esri/core/workers/init.js:226:109)\n at f.fromBuffer (https://js.arcgis.com/4.23/esri/views/2d/layers/features/Pipeline.js:792:11)\n at g.<anonymous> (https://js.arcgis.com/4.23/esri/views/2d/layers/features/Pipeline.js:711:522)\n at Generator.next (<anonymous>)\n at h (https://js.arcgis.com/4.23/esri/core/workers/init.js:58:236)\n at q (https://js.arcgis.com/4.23/esri/core/workers/init.js:62:427)"

Error: Invalid data type

 

 

0 Kudos
7 Replies
Ke_Xu
by Esri Contributor
Esri Contributor

Hi @MKa 

This issue is similar to BUG-00016497: Failed to zoom into the record in ArcGIS Experience Builder when the service is switch....   

It is related to the JS API. When the Service Runtime is set to "ArcMap," it does not support pbf queries, using json queries instead, which works fine. However, when the Service Runtime is switched to "ArcGIS Pro," it utilizes pbf queries but returns no results.

The workaround is republishing the service from ArcGIS Pro.

 

Thanks,

Ke

0 Kudos
MKa
by
Frequent Contributor

Are you saying that my feature service that I point to in my Experience Builder app has to be updated.  My admin says he ran the batch upgrade process on the Feature Service previously created in ArcMap to get it to ArcGIS Pro when he upgraded the Runtime.  We need to run the manual process?  The Feature layer does load, but when we apply a query to it we get the above errors.  We will try your fix and get back to you, but would like to know how the layer loads on the Experience builder map, but the query causes this problem to show up.

 

Right now, When I look at our feature layer in question it shows the supported query formats like below 

Supported Query Formats: JSON, geoJSON, PBF

Doesn't this look right, or do we have to do the publish using ArcGis Pro and it should be good.

0 Kudos
Ke_Xu
by Esri Contributor
Esri Contributor

You needn't to run the manual process. Batch upgrades and manual upgrades yield the same results. 

Ke_Xu_0-1737682240256.png

I think it is related to the above bug. Could you try to republish one service from ArcGIS Pro?

 

Thanks,

Ke

0 Kudos
MKa
by
Frequent Contributor

Now I am not sure that the PDB error is the exact cause of the problem.  I made a simple Experience Builder app with a map and a table.  And added some worldwide polygons that we have from various countries.  When I click on the table for some polygons in South America and Africa and "Zoom To" it works.  When I try it with some other fields, most notably the North American fields, the map goes blank.  In the Developer Tools of browser i see this for the North America fields but not for some other world wide fields.  

{"error":{"code":400,"message":"Unable to complete operation.","details":["Unable to perform query operation."]}}

This is the response from the query when you click Zoom To on the Experience Builder Table.  I believe the Geometry is bad on the request, as if I change this 

 

{"spatialReference":{"latestWkid":3857,"wkid":102100},"xmin":-10517123.595814211,"ymin":-99926432.82529502,"xmax":-10516512.09958793,"ymax":-99925821.32906874}

To pretty much anything else it goes through or at least doesn't give an error.  This is all OOB widgets, only my data is from me.  I am guessing my geometry is bad somewhere, but not sure why the Update to the ArcGIS Pro Runtime made this happen?

0 Kudos
MKa
by
Frequent Contributor

It seems that when I publish my feature service and use the web map in Experience builder, everything in northern hemisphere returns this error.  I add the Web Map to my experience builder, then add one of the layers as a table widget.  When I click on any polygon in the table that is in the northern hemisphere it returns a network error with 440 "Unable to perform query operation.".  It appears that when it attempts to use the YMax/YMin and query my feature service/layer it is unable to do so?  

This worked publishing in ArcMap, but ArcGIS Pro Runtime is causing this issue when it didn't previously.  My data seems to not be able to be queried from Experience builder.

What is strange, is that when I add the layer individually to Experience Builder outside of the web map. I can add it as a table sheet and zoom to it fine.  But when I add that same layer from the Web Map to a sheet and zoom to it, it fails with blank screen and PBF and 400 errors.  

 

0 Kudos
Ke_Xu
by Esri Contributor
Esri Contributor

Hi @MKa,

Do you encounter this issue when publishing your data from ArcGIS Pro directly? 

 

Thanks,

Ke

0 Kudos
MKa
by
Frequent Contributor
Yes we did.

Whenever we publish a database layer as a feature layer it seems to be
happening in experience builder. Only for the zoom to function of the table
or the code?
The layer draws correctly and you can select/indentify, but something about
the geometry of northern hemisphere is causing the issue.

We are able to copy a small subset of the data to the machine ArcGIS pro is
running on, publish as feature layer, and that works. But that doesn’t work
for what we need. When we try and publish that same small subset from our
database we continue to have the zoom to issue

0 Kudos