Latest Contributions by MattStayner

We have an app listing in the ArcGIS Marketplace. Users who want to access our app using their ArcGIS Online credentials simply sign up for the app on the Marketplace and provision the user with the appropriate licensing. It works great! I want to sign up for my own app so I can create a sample account. When I view my app, the "Free Trial" button is disabled and I see options to edit my listing instead (see below). How do I sign up for my own app on the ArcGIS Marketplace? Thanks! Matt ... View more

Hi AppStudio Team! I need to bring ArcGIS Runtime into Survey123 so I can sync feature services. I saw Erwin answered a similar question previously, but my situation is slightly different, so I thought it would be best to create a new thread. I asked about this over on the Survey123 forum. James Suggested we look at using parallel portal objects. We tried creating a parallel Portal object and we were able to get sync working (yeah!), the only problem is we have to sign in twice - once for the Survey123 portal object and once for the runtime object.  Below is the code we are currently using. We will always be signed into Survey123 and have an Esri user access token when we run sync. Is it possible to create a new portal object using an access token instead of a username and password?  var portal = ArcGISRuntimeEnvironment . createObject ( "Portal" , { url : " https://www.arcgis.com " } ) ; var credential = ArcGISRuntimeEnvironment . createObject ( "Credential" ) ; credential . username = "[portal username]" ; credential . password = "[portal password]" ; portal . credential = credential ; portal . loadStatusChanged . connect ( function ( ) { if ( portal . loadStatus === Enums . LoadStatusLoaded ) {   var info = portal . portalInfo ;   var licenseInfo = info . licenseInfo ;   // update licence Info   ArcGISRuntimeEnvironment . setLicense ( licenseInfo ) ;   console . log ( "licensceLevel after Update:" + ArcGISRuntimeEnvironment . license . licenseLevel ) ; } ‍‍‍‍‍‍‍‍‍‍‍‍‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ Thanks! Matt ... View more

I have a web app that uses OAuth2 to authenticate Esri named users. I have an access token for the user and, if the feature service is "secured" (not shared with public), I append the token to the feature service to load it (e.g. "[feature service url]?token=[token]") . It used to be that if I appended the token to a "public" feature service (share with everyone), then I would get an error and the service wouldn't load. That meant I would have to track which services were "secured" and which were "public" and request the data accordingly. I noticed on AGOL the other day when I looked at the details page of a "public" feature service that an access token was appended to it. I thought that was interesting, so I started experimenting. It appears that I can now append an any Esri access token to a "public" feature service and it will still load as long as the token is valid. I have 3 questions on this topic: Is my understanding correct, that you can append an access token to a "public" feature service and it will still load? If that is correct, when was the change made? Is it documented somewhere? Will that always work in the future? If so, I am going to simplify my codebase and always append an access token to feature services. If it is uncertain, I might need to leave it all in "just in case". Thanks! ... View more