|
IDEA
|
I would like to apply theme-grid to individual groups in a survey, rather than the whole survey itself. Often, there are only a few questions in a longer survey that I may want to consolidate onto a single line, this is where I would find this option useful. Reasoning: This could potentially help to work around the incompatibility of theme-grid and table-list in the same survey. Setting theme-grid on the entire survey adds borders to every question which are distracting. Alternatively, if we could set the borderColor property in the body::esri:style column it would be helpful (see separate idea here)
... View more
10-22-2019
03:36 AM
|
31
|
8
|
7876
|
|
POST
|
Hi Brandon, Thanks for the additional info. See attached example, the w appearance was not working as expected because I did not have the "theme-grid" parameter in settings. Unfortunately, the "body::esri:style" setting does not support grid borders, so that coupled with the incompatibility with table-list makes this a less viable option for what I'm trying to do. Using w appearance without theme-grid works if I don't need to set a custom length for a specific question. Is this by design or by chance? It gets me 95% of where I need to be, but I don't want to build this in to my survey if it will cause me heartache down the road (a-la the "supportsApplyEditsWithGlobalId" issue many of us faced a few months back). I suppose at the end of the day, it would be beneficial to be able to apply theme-grid at the group level, and not at the survey level.
... View more
10-14-2019
11:46 AM
|
0
|
4
|
8108
|
|
POST
|
Some brief searches didn't yield anything, but if I've missed a guidance doc somewhere please point me in the right direction. I'm using S123 Connect v 3.6.137. I have a long survey, and I want to place some grouped questions into columns using appearance parameters (w1, w2, etc.). Is this supported without using the theme-grid setting for the entire survey? It seems to work, but individual question overrides (i.e. setting a multiline text question to full width) are not working as expected (see screen shots). Alternatively, I can place the whole survey into theme-grid, however there are a few drawbacks that make that less than ideal for me. Mainly, the grid borders are distracting (to my eyes). Is there a way to control border color, weight, and appearance? Also, I have a long Yes/No question list that I currently display in a table-list, and this does not appear to be supported with theme-grid. Am I missing a setting somewhere to make this work? Thanks in advance!
... View more
10-14-2019
06:09 AM
|
0
|
6
|
9176
|
|
POST
|
Thanks Adrian. That is what I am doing now (manually updating symbology after publishing). It would just be nice to have an arrow line style in Pro that was compatible with ArcGIS Online, so you could set the arrow symbol in Pro, then publish a HFS and not have to go into the settings to update the line style after the fact.
... View more
10-14-2019
03:28 AM
|
1
|
1
|
2183
|
|
BLOG
|
I would love to hear if this is available now, particularly in the app. We have a huge survey with 100+ records in the inbox at any given time, each with many attachments. Performance is not great with this setup, so the ability to target a specific feature to edit (in app) would be huge!
... View more
09-11-2019
03:21 PM
|
0
|
0
|
12161
|
|
POST
|
I have a HFS on ArcGIS Online and I need to make some edits. Like most GIS data ,the underlying geodatabase used to publish this service contains subtypes and domains. The data was published this way to AGOL, and both are present when I edit in web apps. However, I need to do heavy geometry editing, which necessitates desktop. Neither Pro nor ArcMap are handling the subtypes well. In ArcMap (10.6.1) when I create a local edit copy, everything seems to work fine until I sync. The new features in the HFS have null subtypes, so I need to go and populate those manually after syncing the edits. I've noticed that the local edit GDB has an underscore appended to the subtype field (i.e. "Subtype_") so I'm guessing there's a bug where this is not mapped back to the "Subtype" field in the HFS. So, on to Pro. When I edit the HFS directly in Pro (2.4.1) the attribute domains are not present for a feature, unless the subtype is null. I've posted about that issue here with no luck yet. I've resorted to making the edits in ArcMap then going through Pro to populate the subtypes after I sync. As you can see, this is pretty inefficient. What am I missing?
... View more
08-14-2019
10:32 AM
|
0
|
0
|
425
|
|
POST
|
I'm having an issue similar to the end of this discussion, where my domains are not recognized in ArcGIS Pro (2.4.1). The data was published with domains intact, and the features are rendered on the subtypes. When I edit in a web app the domains are working as expected, but when I bring the data into Pro for editing, they are not. Field with domains are simply treated as an unbound text field. Interestingly, when I set the subtype to null, the domains re-appear, and then they will disappear again when I set a subtype value. The underlying gdb used for publishing doesn't have subtype-specific domains (i.e. every subtype is using the default domains assigned at the feature class level. Michael Miller or Kelly Gerrow do you have any insight as to what the cause may be, or how to fix this? It's impacting productive editing (just can't do much beyond simple attribute updates in a web app).
... View more
08-13-2019
11:44 AM
|
0
|
2
|
1743
|
|
POST
|
Is the Pro append tool smart enough to grab the attachments and related records too? Or do you need to manually append those?
... View more
06-13-2019
08:21 AM
|
0
|
0
|
1754
|
|
POST
|
I tried to use this script (via a toolbox, added new script and pointed to the .py fle) and it runs in less than 1 second with no output. Any ideas on how to figure out what's going on? I also tried pasting the code directly into the python window in catalog and running it that way (both times I updated the scrip to hard code the path to sqlite db and the out folder ) wit no luck.
... View more
06-07-2019
09:35 AM
|
0
|
0
|
6623
|
|
POST
|
James Tedrick I too am unable to export to file GDB from the survey123 site (see attached error message), though I am able to export the HFS directly from the AGOL site. This is only happening for some surveys.
... View more
06-04-2019
05:27 PM
|
0
|
1
|
2399
|
|
POST
|
Thanks Xander Bakker See example here: http://arcg.is/1Tzjiq There is one layer with the code in my original post, which does not produce a label. There is a second layer with the code shown below that does produce a label. //Returns Diameter and/or material excluding -999 and Unk values
function GetMainLabel(Dia,Mat) {
return When(Dia !=-999 && Mat != "Unk", Dia + "'' " + Mat, Dia !=-999 && Mat == "Unk", Dia + "''", Dia ==-999 && Mat != "Unk", Mat,"")
}
// Set MinLabel value as the minimum feature length to be labeled:
var MinLabel = 50;
var PipeLen = $feature.SHAPE__Length; //var PipeLen = Length(Geometry($feature), 'feet');
iif (PipeLen >= MinLabel, GetMainLabel ($feature.NominalDiameter,$feature.Material),''); Regarding the length, that's actually commented out and the length is taken from Shape__Length. However, the data was in NJ State Plane when published, and it's my understanding that it stays that way and gets projected on the fly in AGOL. Is this not correct? The spatial reference WKID is 102711 (NJ state plane NAD83)per the json (see screen shot)
... View more
05-22-2019
08:23 AM
|
0
|
2
|
2183
|
|
POST
|
I wrote the label expression below to look at pipe length and cross section shape to determine if and how a label is generated for a pipe. It works fine in ArcGIS Pro, and when I paste the expression into ArcGIS Online the code validates and returns a test string as expected (for both label functions in the expression). However, no labels are displaying on the map. I have a similar (and more simple) function that is working just fine. function ChooseLabelFormat(ML,PL,Sec){
//Calls the label function based on pipe shape
return When(
PL >= ML && Sec == 'Circular', GetMainLabel ($feature.NominalDiameter,$feature.Material),
PL >= ML && Sec != 'Circular', GetMainLabelNC ($feature.Material,$feature.BoxHeight,$feature.BoxWidth),
"")
};
function GetMainLabel(Dia,Mat){
//Returns Diameter and/or material excluding -999 and Unk values
return When(
Dia !=-999 && Mat != "Unk", Dia + "'' " + Mat,
Dia !=-999 && Mat == "Unk", Dia + "''",
Dia ==-999 && Mat != "Unk", Mat,
"")
};
function GetMainLabelNC(Mat,BH,BW){
//Returns HeightxWidth and/or material excluding -999 and Unk values
return When(
BH !=-999 && Mat != "Unk", BH + "'' x " + BW + "'' " + Mat,
BH !=-999 && Mat == "Unk", BH + "'' x " + BW + "'' ",
BH ==-999 && Mat != "Unk", Mat,
"")
};
//Set variables and call function for labeleling
var Section = DomainName($feature, 'CrossSectionShape');
// Set MinLabel value as the minimum feature length to be labeled:
var MinLabel = 50;
var PipeLen = $feature.SHAPE__Length; //var PipeLen = Length(Geometry($feature), 'feet')
return ChooseLabelFormat(MinLabel,PipeLen,Section);
... View more
05-21-2019
04:37 AM
|
0
|
4
|
2550
|
|
POST
|
None of my users can access surveys via the website this morning. There have also been a lot of random time outs and generally poor performance with the website over the last week or 2. Is Esri aware of these issues?
... View more
05-13-2019
05:12 AM
|
0
|
1
|
560
|
|
POST
|
I came across this issue and my resolution was similar, thought I'd share to help anyone else in the future If you published your data with a definition query on it (in my case from a file GDB from ArcGIS Pro 2.2.4), and your edit template for the hosted feature service does not satisfy that definition query, you cannot create new features in that feature service. Updating the template to satisfy the definition query will resolve the issue. This is an odd one, since that definition query no longer has an bearing on the data (you can then go ahead and edit the new feature to fall outside of that definition query). Also, if you've configured a layer on your hosted feature service to enforce an attribute as unique, and your template does not provide a value for that attribute, a new feature cannot be created. Similarly, if you attempt to add a new feature that's duplicating that unique attribute, the feature will fail to create (no warnings provided).
... View more
05-01-2019
05:46 AM
|
0
|
0
|
3918
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-20-2026 04:14 AM | |
| 1 | 07-01-2025 05:11 AM | |
| 1 | 06-13-2022 11:18 AM | |
| 9 | 05-22-2025 04:45 AM | |
| 4 | 04-12-2024 09:00 AM |
| Online Status |
Offline
|
| Date Last Visited |
03-20-2026
04:11 AM
|