Latest Contributions by BrianBerdel

Hi Phil, I'm actually trying to do the same thing with Assignee LIKE ('%' + ${username} + '%') in a survey123 Inbox, I see you say about Disabling Standardized Query security Option. How do I get to that point though? I found this Help Page but the link they provide doesn't lead anywhere - https://gisserver.domain.com:6443/arcgis/admin I've been googling for a while and cannot find how to login to the correct page to disable this option. Any help would be appreciated thanks. UPDATE:  It seems there's a conflicting message here concerning disabling standard queries.  On one hand we're told we need to disable standardized queries in order to use the ${username} function in a query, then we're told it's no longer an option in ArcGIS Online as of June 2020... FAQ: What are the implications of the June 2020 ArcGIS Online Standardized SQL Query Enforcement?  We're at a crossroads here where we've got 15 field user licenses that are mostly useless if we can't query the inbox by username.  This thread and others have been clear that standardized query needs to be disabled but there needs to be some guidance on how to use that username function now that we can't disable standardized query security.  ... View more

During republishing, I've been stuck at the publishing screen for 30 minutes now. There are about 1,400 records in my feature layer. Is it normal to take this long deleting the service item, or should I abort and try starting over or try copying the survey? ... View more

I tried using the attribute directly originally and it still wouldn't display the value even when the field was filled out. That's when I tried to use expressions and that didn't work either. Is there a reason why the direct attribute wouldn't display even though the field is filled in? ... View more

I did, they're labeled 1., 2., 1. or is    return($feature.-----) not an expression? ... View more

Here are two expressions that shows correctly in the popup 1. return($FEATURE.ST_RT_NO)    - {expression/expr7 2. return($feature.street)    - {expression/expr8}  In the Custom Attribute Display I put the below statement    - State Route {expression/expr7} - {expression/expr8}     - And received the correct information --> For the one that isn't working 1. return($Feature.RESTRICTION_TYPE)      - Restriction Type - {expression/expr15}      - And it's doesn't populate ... View more

I just figured this out. Here's what I did: I made a class to represent the Esri Field object: [Serializable] public class ESRIFeatureLayerFieldDefinition { public string name { get; set; } public string type { get; set; } public string alias { get; set; } public string sqlType { get; set; } public int length { get; set; } public bool nullable { get; set; } public bool editable { get; set; } public string domain { get; set; } public string defaultValue { get; set; } } from there I created a test field and added it to a list: ESRIFeatureLayerFieldDefinition addField = new ESRIFeatureLayerFieldDefinition(); addField.name = "TestField14"; addField.type = "esriFieldTypeString"; addField.alias = "TestField14"; addField.sqlType = "sqlTypeOther"; addField.length = 150; addField.nullable = true; addField.editable = true; addField.domain = null; addField.defaultValue = null; List<ESRIFeatureLayerFieldDefinition> fieldList = new List<ESRIFeatureLayerFieldDefinition>(); fieldList.Add(addField); Next, I put that list into a dictionary of type string, object, and gave it a key of "fields": Dictionary<string, object> fieldArray = new Dictionary<string, object>(); fieldArray["fields"] = fieldList; I created my RestRequest, specifying it as a "POST" method along with the URL to my service: RestRequest request = new RestRequest(url, Method.POST); request.Method = Method.POST; Then I added a parameter for the fields. The only thing is, the service is looking for a parameter called "addToDefinition" that CONTAINS the fields object. (I found this out after using fiddler to analyze the request when I submitted a request through esri's web admin interface). So, I have only one parameter in my request and it looks like this: request.AddParameter("addToDefinition", serializer.Serialize(fieldArray), ParameterType.GetOrPost); The "addToDefinition" is the name of the parameter that the REST service is looking for. I used a serializer to serialize the fieldArray dictionary object to get the fields JSON object as a string. Parameter type was GetOrPost, and since it's only one it will be passed as the body of the request. Any additional querystrings or parameters "f=pjson", "token=" were all appended to the resource URL for my request object. Once that request completes, you should see the new field in your service definition. ... View more

I just figured this out a few minutes ago (after a couple weeks of trying). I was trying to make this request from a C# backend using RestSharp libraries. Here's what I did: I made a class to represent the Esri Field object:     [Serializable]     public class ESRIFeatureLayerFieldDefinition     {         public string name { get; set; }         public string type { get; set; }         public string alias { get; set; }         public string sqlType { get; set; }         public int length { get; set; }         public bool nullable { get; set; }         public bool editable { get; set; }         public string domain { get; set; }         public string defaultValue { get; set; }     } from there I created a test field and added it to a list:             ESRIFeatureLayerFieldDefinition addField = new ESRIFeatureLayerFieldDefinition();             addField.name = "TestField14";             addField.type = "esriFieldTypeString";             addField.alias = "TestField14";             addField.sqlType = "sqlTypeOther";             addField.length = 150;             addField.nullable = true;             addField.editable = true;             addField.domain = null;             addField.defaultValue = null;                                     List<ESRIFeatureLayerFieldDefinition> fieldList = new List<ESRIFeatureLayerFieldDefinition>();             fieldList.Add(addField); Next, I put that list into a dictionary of type string, object, and gave it a key of "fields": Dictionary<string, object> fieldArray = new Dictionary<string, object>();             fieldArray["fields"] = fieldList; I created my RestRequest, specifying it as a "POST" method along with the URL to my service:                         RestRequest request = new RestRequest(url, Method.POST);             request.Method = Method.POST; Then I added a parameter for the fields.  The only thing is, the service is looking for a parameter called "addToDefinition" that CONTAINS the fields object.  (I found this out after using fiddler to analyze the request when I submitted a request through esri's web admin interface). So, I have only one parameter in my request and it looks like this:             request.AddParameter("addToDefinition", serializer.Serialize(fieldArray), ParameterType.GetOrPost); The "addToDefinition" is the name of the parameter that the REST service is looking for.  I used a serializer to serialize the fieldArray dictionary object to get the fields JSON object as a string.  Parameter type was GetOrPost, and since it's only one it will be passed as the body of the request. Any additional querystrings or parameters "f=pjson", "token=" were all appended to the resource URL for my request object. Once that request completes, you should see the new field in your service definition. ... View more