Select to view content in your preferred language

Upgrading to 4.28 - outFields contains invalid or missing fields

664
3
Jump to solution
12-12-2023 03:50 AM
michaelkdev
New Contributor III

Unsupported query - using type: blob. 
https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-Field.html#type

error.png

 

 

Documentation:

Possible Values:"small-integer"|"integer"|"big-integer"|"single"|"double"|"long"|"string"|"date"|"date-only"|"time-only"|"timestamp-offset"|"oid"|"geometry"|"blob"|"raster"|"guid"|"global-id"|"xml"

 

 

0 Kudos
2 Solutions

Accepted Solutions
UndralBatsukh
Esri Regular Contributor

You are getting this error likely because the field you are running the query on does not exist on the layer or the layer view. Try setting the FeatureLayer.outFields property to include the fields you want to work with. 

View solution in original post

0 Kudos
UndralBatsukh
Esri Regular Contributor

Hi there, 

Ah yes this is a known issue at 4.28. This issue will be addressed in 4.29 and the fix is already in `next`. You can update your codepen to point to  <script src="https://js.arcgis.com/next/"></script> to check the fix. 

Hope this helps,

View solution in original post

0 Kudos
3 Replies
UndralBatsukh
Esri Regular Contributor

You are getting this error likely because the field you are running the query on does not exist on the layer or the layer view. Try setting the FeatureLayer.outFields property to include the fields you want to work with. 

0 Kudos
michaelkdev
New Contributor III

Seems like there's an issue with the queryFeatures query with outFields and type 'blob' 

I made a Codepen to reproduce it (check console.log). @UndralBatsukh 

https://codepen.io/michaelk95/pen/PoVroJv 

(Run 2 times to get the full error message)

Thanks

0 Kudos
UndralBatsukh
Esri Regular Contributor

Hi there, 

Ah yes this is a known issue at 4.28. This issue will be addressed in 4.29 and the fix is already in `next`. You can update your codepen to point to  <script src="https://js.arcgis.com/next/"></script> to check the fix. 

Hope this helps,

0 Kudos