Latest Contributions by AdamDaily

‎12-18-2018

Jim, The problem with adding an if statement is there is no field I can use for that to work properly. For example, all of my features have asset_tag values, thus eliminating the default "Small" to ever appear in my kickplate field. I could use another field to return null, thus making the default "Small" to appear, but then that voids my pulldata function. I end up overwriting existing data I want to keep with inaccurate default data (asset_tag=null so kickplate = Small, but my table shows kickplate = Medium for that feature). The work around is to use 2 fields, 1 text field "kickplate1" using pulldata, and 1 select_one field "kickplate2", only relevant and with default values if "kickplate1" is null. The obvious problem here is having to create 2 fields for capturing each attribute. What I really need to be able to do is say IF "my pulldata function" = null, then activate the default value. And to go 1 step further, to have that statement in a select_one field type. By default, my pulldata functions are already void in any select_one fields. So select_one overwrites pulldata, and pulldata voids default values. So it appears here that my best option is just to eliminate the calculation completely.

‎12-14-2018

Thanks Jim, That is probably what is happening. I didn't think of that because those fields really don't have much data in the dataset to pull from, but I know the pulldata & select_one functions don't play well together so it is likely it won't work with defaults either. Thanks for looking into it.

‎12-13-2018

Jim, Please see the attached file. I was trying to set fields "vision_light" to default "none", kickplate to default "small", bumper to "No", and thickness to "1.75"

‎12-10-2018

Thanks Jim for the answer, I wanted to confirm there wasn't something else I was missing. That is exactly what I tried (also tried with quotes when that didn't work), but the default values are not appearing in Survey Connect testing, or after publishing and downloading my survey. No default field values set for any select_one questions are coming through.

‎12-07-2018

Can you take a value from a select_one question list and set one of those values as the default answer to that question? I feel like I have done this before but it is not working in my current survey. I must be putting this in wrong. Expl: Choices are Small, Medium, Large, and I want my question to default the answer as "Small"

‎10-05-2018

Thank you, That would be a big help. Can you please reply again to this thread when the that fix has been made. Right now I am offsetting our date range filters by 1 day on the back end to include the "to" date within the range.

‎10-01-2018

I know survey time stamps submitted data 8 hours ahead of Pacific Coast time zone (my location) due to the WGS coordinate system it uses. Since the time stamp is a hidden attribute, and the creation date field is turned off by default when viewing data in Survey123 website, this can create big problems when extracting data using a date range filter if this variance is not accurately accounted for. Recently I discovered a new problem when using the "in between" date filter. Survey does not consistently filter data correctly, leaving out features that fall within my date range. For example, my date filter is set to return all created features between 9/14 and 9/26. I get features from 9/14, but nothing from 9/26. At first I thought features were getting dated on the following day since they are time stamped 8 hours into the future, but that was not the case. The same filter set to 9/14 and 9/27 now returns those missing records, still dated 9/26. We regularly extract survey data based on very specific date ranges. I am concerned that between the time stamp difference and inconsistent filtering, we maybe missing large amounts of collected data. What is causing this and is there a solution to fix this issue?

‎09-18-2018

These supported formats are for Pro, would it matter that I'm using desktop/catalog and not Pro? I've noticed a number of other arc toolbox tools that I use regularly in model builder that suddenly don't work well when exported to python.

‎09-17-2018

I was able to get Iterate Feature Classes to work with Feature Class to Geodatabase to output CAD layers to a empty geodb. This still doesn't work well however, since I can't tell it which CAD files I want to use for iteration. I end up processing many files I don't need or want. The wildcard in the iterator doesn't work when the name you want to search for in in the middle of a file name. Example: I have a folder with lots of CAD files all with different naming conventions. I want to use wildcard to keep only CAD layers with a string "value" in the file name: "data-1 my value.dwg", "data-1_yourvalues.dwg", "some_other_value1.dwg". - Cant use *value* or value*. Is there any way to do this?

‎09-17-2018

Adrian, Thank you for the reply and for posting those links. I had seen those threads previously, and I have tried the iterate dataset & feature class to feature class, as well as iterate feature class & copy methods he describes. Neither version returned anything for me except empty outputs and generic error messages. I'm not able to copy the CAD data using any of these tools connected to an iterator. The only way that has worked so far is using "append" outside of iterating, by matching up every CAD file separately in my model to its created database layer (which I do not want to do for entire directories of CAD files). I'm wondering if there is some compatibility issue with model builder reading newer CAD files?

‎09-14-2018

I've tried every way I could find to iterate through a file directory, extract CAD files, and then copy the CAD lines to a geodatabase. I want to avoid having to append each dataset individually to a matching db layer. I tried using a number of tools and combinations of tools and settings, creating new feature classes vs using existing ones. I am using Arc 10.6, and Autodesk 2018. Nothing works. All I get are errors and empty outputs. I'd like to do this in model builder but wondering if it is even possible? None of these tools seem to do what they say they do. Just a few of the many things I've tried are shown below. Can anyone point me to a workflow that actually works? Feature Class to Feature Class CAD to Geodatabase Copy Features Copy Collect Values Create Feature Layer

‎09-13-2018

If the missing survey data was captured in the sqlite db, the entire survey should appear in 1 very long text field. Try exporting that table to excel and delimit the data. You can then match your fields up and append the delimited data back to a geodb or AGOL.

‎08-03-2018

James, I went back and took a look at my pull-data tables. The classification codes I had for the features that were not working properly were longer integers then all of the others. Thank you for looking at this and leading me to the issue, that absolutely was what was causing that error. Fixing that line in my csv file fixed everything in my survey. Thank you!

‎08-02-2018

James, I was experimenting with that field as I noticed my pulldata calcs stopped working correctly depending on the field value type of "classification". I have multiple other surveys constructed similarly, all set up with that "classification" field set to integer (not thru bind:esri). I was using text with bind:esri Integer to try and fix my pulldata functions. This seems to be another/unrelated issue. My underlying feature service "classification" field is set to integer. I have 6 other surveys writing to that same service and all seem to be working ok when submitting completed surveys. It is just this 1 survey, and only certain feature types within it "FM200" being the main one, (out of 7 surveys and probably 50 or so feature types) that produce this error and will not send. I have tried using text and integer in the field "classification", but that seems to be unrelated to whatever is causing this issue. Is it possible to change a field type in the underlying feature service as well as make that change to that field in my surveys writing to it, without taking down the entire service and republishing all of the surveys?

‎07-26-2018

Philip, I thought I had the issue fixed, but even after rebuilding the survey and testing (seemed fine during testing in Connect), after publishing our field crew is getting the same error message. I'm not sure what else to check at this point.

Online Status	Offline
Date Last Visited	‎01-12-2021 04:09 PM

My Ideas

Latest Contributions by AdamDaily

Re: Default value for a select_one question type

Re: Default value for a select_one question type

Re: Default value for a select_one question type

Re: Default value for a select_one question type

Default value for a select_one question type

Re: Time Stamp and Date Range Filter Problems

Time Stamp and Date Range Filter Problems

Re: Iterate File Directory and Copy CAD Lines to Geodatabase in Model Builder

Re: Iterate File Directory and Copy CAD Lines to Geodatabase in Model Builder

Re: Iterate File Directory and Copy CAD Lines to Geodatabase in Model Builder

Iterate File Directory and Copy CAD Lines to Geodatabase in Model Builder

Re: Copy sent data to new survey or edit existing survey tools not working

Re: Arithmetic Overflow send error and Converting XLSForm error

Re: Arithmetic Overflow send error and Converting XLSForm error

Re: Arithmetic Overflow send error and Converting XLSForm error

Re: Wrong info populating from pulldata()

Re: Is there a field limit in AGOL web map layers ...

Re: Format decimal place in ArcGIS Pro

Re: ArcGIS Online - Multiple Feature Services/Sing...

Re: Writing to multiple services/tables