Latest Contributions by RobStauder

‎11-01-2020

Hi all, I wonder if anyone has run into this issue and figured out a workaround for it? AppStudio 4.3.193 on windows 10 Two monitors - one is a laptop screen and the other a sizeable desktop monitor. Monitors are set to extend in windows display. Start AppStudio and move it to the secondary monitor (not Main Display) Start one of the samples (eg Feature Layer) in the QT Editor debugger At this point, the sample app will hang. The last line printed to the QML Debugger Console is void __cdecl QmlApplication::initialize(void) As long as I start the debugger from the Main Display, everything works. I can change which monitor is Main and as long as I run from the Main display, everything works. I can also duplicate the monitors and it works.I can start the app from the Main screen and then move it to the secondary screen - this also works. It only seems to hang when I start the app from the secondary monitor. The background for this and reason for this post is that I'm creating an app for a client and they will definitely be running on workstations with multiple monitors. Ideas? Thanks, Rob

‎10-04-2020

Hi Ryan, Not sure if it's too late on this one but here's what I did for file based datasets (kml/kmz and shapefiles): 1. Use the DocumentDialog type. It's in beta and doesn't allow you to filter by file extensions (lol) - FileInfo { id: fileInfo } DocumentDialog { id: fileDialog onAccepted: { // add the attachment to the feature table fileInfo.url = filePath var lyr = createFromFile(fileInfo); mapView.map.operationalLayers.append(lyr); } } function createFromFile (file_info) { //read file extension - is it .shp or .kml/kmz? var ext = file_info .suffix var file_path = file_info .url if ( ext === 'kml' || ext === 'kmz' ) { // create the dataset from a local file const kmlDataset = ArcGISRuntimeEnvironment .createObject( "KmlDataset" , { //url: AppFramework.userHomeFolder.fileUrl(caKmlPath + "/SubDivs.kmz") url: file_path }); // create the layer const kmlLayer = ArcGISRuntimeEnvironment .createObject( "KmlLayer" , { dataset: kmlDataset }); // return the KML Layer return kmlLayer ; } if ( ext === 'shp' ) { const shpFeatTbl = ArcGISRuntimeEnvironment .createObject( "ShapefileFeatureTable" , { path: file_path }); const shpLyr = ArcGISRuntimeEnvironment .createObject( "FeatureLayer" , { featureTable: shpFeatTbl }); return shpLyr ; } } 2. Enable drag and drop on the map. This was awesome! DropArea { id: dropOnMap anchors.fill: parent FileInfo { id: dropFileInfo } onEntered: { if (drag.urls.length === 1) { // verify that this file exists dropFileInfo.url = drag.urls[0]; if (dropFileInfo.exists) { if (validateFileExtension()) { //just checks for kml/kmz + .shp drag.accept(); } else { console.log( "Not KML/KMZ or Shp" ); } } } } onDropped: { if (validateFileExtension()) { var droplyr = createFromFile(dropFileInfo); mapView.map.operationalLayers.append(droplyr); } } Best of luck w/your work! Rob

‎06-15-2020

Hi all, Just following up on this. Everything is working quite well with the 33+ attribute rules updating a single feature class. The rules are pulling values from different source layers, some of which have several million rows. I'm super impressed at how powerful attribute rules can be. Rob

‎02-19-2020

Hi all, I'm looking for some friendly advice or opinions on this one. I'm configuring a Survey123 + Ops Dashboard solution that uses attribute rules to pull data values from some source layers into the Survey123 feature service. The survey is hosted in an eGdb and shared through portal. Currently, I have 5 attribute rules defined on the Survey123 layer and things seem to be happy. The plan is to create 33 total attribute rules. 32 of the 33 will use the intersects function (point in poly query). The other attribute rule calculates a score from the 32 values set by the other 32 rules. My question: Is this, perhaps, a poor design decision? Anyone have a sense of how this might behave? For every point created by Survey123, 33 rules will fire, updating 33 fields. None of the data will be versioned. Use of the solution won't be too extensive but will be global in coverage. I think a reasonable expectation is 500 responses over 3-6 months. Portal and database have massive capacity. Any thoughts? Thanks, Rob

‎01-21-2020

Hi all, Wondering if anyone has run into this? In Survey123 Connect - create a new survey from the Advanced Template Open the XLSForm in Survey123 Connect Add a question - type = Image, name = img_annotate, Label = annotate me!, appearance = annotate Publish to portal/enterprise 10.7.1 Access the web form version of this survey - eg: https://survey123.arcgis.com/share/<item id thing>?portalUrl=https://someportal.com/portal Click in the annotate me input box and upload a small image. Click submit - fails with The upload request returns this - {"error":{"code":403,"subcode":52,"message":"Error performing upload operation, File size or type not supported for this service","details":[]}} Republish the survey without the annotate appearance - now it works upon submit. Only, we don't have the option to annotate in the web form. Any ideas what could be going on here? Workarounds? Rob

Online Status	Offline
Date Last Visited	‎01-20-2021 09:09 AM

My Ideas

Latest Contributions by RobStauder

Strange hanging issue

Re: "Add Data" widget for AppStudio

Re: Limit on number of attribute rules?

Limit on number of attribute rules?

Image question w/annotate appearance fails on submit on portal?