Latest Contributions by MKa

I know how to connect to a portal and AGOL.  I just want to populate the ArcGIS.com organizational URL with "MyCompany".  I have tried all of the registry tricks, changing AuthPortal, changing json files.  I just cant get this prepopulated.  If I can get this prepopulated I don't have to add my org portal directly and switch between them.  I need to keep ArcGIS.com active as my MyCompany.maps.arcgis.com uses ArcGIS.com for Token auth i am guessing.  So we have to log into both regardless.  I just want to prepopulate this for my users on first load or ArcGIS Pro install of my addin.  I am wondering what I am missing here, I have tried to solve this with AI and updating Registry and Files.  Just wondering if someone could clear out their portal list except for ArcGIS.com, sign out of all of them, load ArcGIS Pro and have that box prepopulated with a value.  I don't want to add a seperate portal to the list, ArcGIS.com entry will do everything I want once I put in the Org URL and sign in.  As it handles all requests and Authentication.     ... View more

My experience builder version was old, but we had to upgrade the Runtime.  So in order to fix this I created an interceptor widget to turn the PBF into JSON for some URLs.  I added that widget to my map and intercepted the urls i wanted.  The Runtime It was adding numbers to lat long in northern hemisphere in PBF for some reason, json did not. i import { moduleLoader } from 'jimu-core'; import React, { Component } from 'react'; class InterceptorWidget extends Component { render() { (async () => { const [esriConfig] = await moduleLoader.loadModules(['esri/config']); console.log("loading esri/config:" + esriConfig); const myInterceptor = { urls: [ /\/server\/rest\/services\/Web\/Web2\/FeatureServer\/.*/, /\/server\/rest\/services\/Web\/Web2Buffer\/FeatureServer\/.*/ ], before: function (params) { //We intercept the pbf on the first call, All subsequent calls seem to follow the json rule, so after the first intercept this works if (params.requestOptions.query.f == 'pbf' && params.requestOptions.query.resultType != 'tile') { console.log('INTERCEPTED request:', params); console.log('INTERCEPTED request params.url = ' + params.url) params.requestOptions.query.f = 'json'; } else { //console.log('SKIPPED esriConfig.request params.url = ' + params.url) //console.log('SKIPPED params.requestOptions.query.f = pbf = ' + params.requestOptions.query.f ) //console.log('SKIPPED params.requestOptions.query.resultType = ' + params.requestOptions.query.resultType) } } }; esriConfig.request.interceptors.splice(0, 0, myInterceptor); })(); return ( <div> {/*         <h1>InterceptorWidget</h1> */} </div> ); } } export default InterceptorWidget; ... View more

That worked.  I added the code as a widget and added to an experience to intercept the query.f == 'pbf' with query.f = 'json'.  The only thing i don't understand is why I only had to do the intercept once, meaning it only hits the breakpoint on the first call.  All subsequent calls to same url don't reach the "before" breakpoint.  Anyways, this was the solution i was looking for.  Here is the test widget for others with this problem.  This was build with ExB 1.8.   import { moduleLoader } from 'jimu-core'; import React, { Component } from 'react'; class MyCustomWidget extends Component { render() { (async () => { const [esriConfig] = await moduleLoader.loadModules(['esri/config']); console.log("loading esri/config:" + esriConfig); const myInterceptor = { urls: [/\/server\/rest\/.*/], before: function (params) { //We intercept the pbf on the first call, All subsequent calls seem to follow the json rule, so after the first intercept this works if (params.requestOptions.query.f == 'pbf' && params.requestOptions.query.resultType != 'tile') { console.log('Intercepted request:', params); console.log('esriConfig.request params.url = ' + params.url) params.requestOptions.query.f = 'json'; } else { console.log('SKIPPED esriConfig.request params.url = ' + params.url) console.log('SKIPPED params.requestOptions.query.f = pbf = ' + params.requestOptions.query.f ) console.log('SKIPPED params.requestOptions.query.resultType = ' + params.requestOptions.query.resultType) } } }; esriConfig.request.interceptors.splice(0, 0, myInterceptor); })(); return ( <div> <h1>Interceptor Widget</h1> </div> ); } } export default MyCustomWidget;   ... View more

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 ... View more

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.     ... View more

I think I am having this same issue.  I am using OOB Experience Builder and getting PBF errors on my queries.  My feature service only has "Supported Query Formats: JSON" while my layers have  "Supported Query Formats: JSON, geoJSON, PBF".   Where do i make your above change? ... View more

This appears to still be an issue that I cannot resolve?  I have a feature service that when I "Zoom to" one of the records it comes back with the error of "Error while parsing FeatureSet PBF payload".   ... View more

Did anyone ever figure our what caused this issue and how to resolve it?  I have tried almost everything but still have problems with some of my layers ... View more

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? ... View more

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. ... View more

Did anyone get a resolution to this?  We just upgraded to the ArcGIS Pro runtime and have the exact same issue with the Feature Services.  Any suggestions would be great and very much appreciated ... View more

I have tried everything.  I even tried creating a map template to load and it still fails.  To reproduce the issue, either uninstall and reinstall ArcGIS Pro 3.3, then run the above configuration code before you ever open ArcGIS Pro by itself, or try and just delete the StrongName folders and then run the above configuration code before you ever open ArcGIS Pro by itself. ... View more