Latest Contributions by KatherinePadilla

‎08-14-2019

Hello, I am trying to do some data cleanup. I am trying to select records that have any fields that do not match the domain assigned. Any ideas on how to do this in ArcGIS Pro? Katie.

‎07-25-2019

Glad it worked out!!

‎07-25-2019

One question, Did you move the survey item from one folder to another in AGO? This may be the issue. I am hope they are working on a solution to solve this issue. It would make file organization cleaner and more effective for us if we have the freedom to move items where we would like them without breaking the link to connect. I have multiple surveys for one program and would like them to all reside in the same folder. This is not a possibility without fully remaking the survey every time there is an update…so for now I am keeping them in separate folders until there is a solution. I did find I could rename the folder without having this issue. Hope this helps.

‎05-01-2019

ok...I am not sure what that means, as most of my questions are in a group already. Could you please expand on that a bit or direct me to documentation that will explain that.

‎05-01-2019

Thank you!!

‎05-01-2019

Here are some notes/observations. Not sure if it will help or not.

‎05-01-2019

I also have this issue. There does not seem to be any pattern in my survey as to which fields are actually requiring the field to filled in or not. I did a test on my survey by opening it, hitting send, then fix what it alerts me to, then try that again. I continued this until it sent. 90% of my survey was not filled in and it was sent and I have required statements all over the place. I have put my xls file here for hopefully an to try it out to see if you can recreate that issue and let me know if there is a solution. Warning this survey is a beast (just under 1300 lines) Thanks!!

‎04-29-2019

I finally figured out what was happening. There are certain instances where I used != in a calculation and the the outcome was different then expected. I had not noticed it before as they were calculate fields and I did not see the outcome. When I found the first one I changed them all to note types and sure enough they all had the issue. Original calculation that produces a long output (see screenshot) if((selected(${EVENT_TYPE},'R_Sample') or selected(${EVENT_TYPE},'R_Resample')) and (selected(${SD_FLOW_OBSERVED_TYPE},'Flowing') or selected(${SD_FLOW_OBSERVED_TYPE},'Tidal')) and selected(${SD_FIELD_SCREEN_IND},'N'),string('NR'),if((selected(${EVENT_TYPE},'R_Sample') or selected(${EVENT_TYPE},'R_Resample')) and (selected(${SD_FLOW_OBSERVED_TYPE},'Flowing') or selected(${SD_FLOW_OBSERVED_TYPE},'Tidal')) and selected(${SD_FIELD_SCREEN_IND},'Y') and selected(${SD_COLOR_TYPE},'Other'),concat(${SD_COLOR_TYPE},',',${SD_COLOR_OTHER}),if((selected(${EVENT_TYPE},'R_Sample') or selected(${EVENT_TYPE},'R_Resample')) and (selected(${SD_FLOW_OBSERVED_TYPE},'Flowing') or selected(${SD_FLOW_OBSERVED_TYPE},'Tidal')) and selected(${SD_FIELD_SCREEN_IND},'Y') and ${SD_COLOR_TYPE}!=Other,${SD_COLOR_TYPE},string('')))) Modified calculation that gets the desired outcome. I tried to shortcut by using the != exclusion but it cannot be combined with other if then statements it seems. if((selected(${EVENT_TYPE},'R_Sample') or selected(${EVENT_TYPE},'R_Resample')) and (selected(${SD_FLOW_OBSERVED_TYPE},'Flowing') or selected(${SD_FLOW_OBSERVED_TYPE},'Tidal')) and selected(${SD_FIELD_SCREEN_IND},'N'),string('NR'),if((selected(${EVENT_TYPE},'R_Sample') or selected(${EVENT_TYPE},'R_Resample')) and (selected(${SD_FLOW_OBSERVED_TYPE},'Flowing') or selected(${SD_FLOW_OBSERVED_TYPE},'Tidal')) and selected(${SD_FIELD_SCREEN_IND},'Y') and selected(${SD_COLOR_TYPE},'Other'),concat(${SD_COLOR_TYPE},',',${SD_COLOR_OTHER}),if((selected(${EVENT_TYPE},'R_Sample') or selected(${EVENT_TYPE},'R_Resample')) and (selected(${SD_FLOW_OBSERVED_TYPE},'Flowing') or selected(${SD_FLOW_OBSERVED_TYPE},'Tidal')) and selected(${SD_FIELD_SCREEN_IND},'Y') and (selected(${SD_COLOR_TYPE},'None') or selected(${SD_COLOR_TYPE},'Yellow') or selected(${SD_COLOR_TYPE},'Brown') or selected(${SD_COLOR_TYPE},'White') or selected(${SD_COLOR_TYPE},'Gray')),${SD_COLOR_TYPE},string(''))))

‎04-24-2019

Here is a related string that I found helpful for this question: Survey123 'username' field is <Null> In short a related bug is being addressed: BUG-000113164

‎04-18-2019

Does the logger indicate what field or fields were truncated? This would be helpful to help me narrow down the search and save some time in trying to locate the error. I tried to review the logger but I don’t understand it. Thanks!

‎04-16-2019

Hello, I cannot figure out what in my survey is truncating. I have attached the xls and the logger. I have gone through the xls twice and cannot find what is going wrong. I tried to look at the logger but I don't quite understand yet how to read these. Any help would be great. Thanks!! Katie.

‎04-12-2019

I had no idea this was the case. I will only use Double moving forward. Thank you! Perhaps this type of information can be included in the types tab of the xls form, or perhaps a hotlink to where they can find more about types of selections. There are likely more people out there that do not have great database understanding that are building surveys and would like to understand better the ramifications of choices they make. Katie.

‎04-11-2019

Hello, I have noticed that there are values in my feature services that have been modified somehow from the time of submission of the survey to when it is written in to the feature service. For example: We fill in decimal fields that are an esriFieldTypeSingle (Float in feature service). We only ever fill in x.xx to the hundredth place, yet when I look at the value in pro and click to edit or export the data, there are a ton more decimal places. This is a huge problem for data integrity. We enter 8.6 for a pH result and the value that is stored in the feature service is 8.60000038. Our pH meters only read out 8.6 or 8.60 that is all there is no way we would have entered 8.60000038. this is not happening for one record or just but all. This is also across different surveys that write to this service. I have also looked at the other services I have and the same thing is happening. This does not happen to fields that are decimal fields that are an esriFieldTypeDouble (Double in feature service) Any ideas what is going on here?

‎03-21-2019

This has worked out great for us, exactly what I was looking for! Thank you so much!!! Katie.

‎03-14-2019

I have moved/renamed the folder in AGO for every single one, but this error does not happen all the time. I’ll have to do more testing to see if that could be the issue. Is there any way around this to where we could be able to move it without a problem? I would like a little more flexibility in where I could save things both in AGO and on the desktop. Thanks!! Katie.

Online Status	Offline
Date Last Visited	‎05-10-2023 08:58 PM

My Ideas

Latest Contributions by KatherinePadilla

Select records that include fields that do not match the domain

Re: Survey123 Connect Frozen when publishing survey

Re: Survey123 Connect Frozen when publishing survey

Re: Can't create if statement in required field?

Re: Can't create if statement in required field?

Re: Can't create if statement in required field?

Re: Can't create if statement in required field?

Re: Send Error: truncated

Re: Survey123 property("username") sometimes null

Re: Send Error: truncated

Send Error: truncated

Re: Decimal Places Added from Survey to Feature Service

Decimal Places Added from Survey to Feature Service

Re: Constraint: No Line Feed

Re: Survey123 Connect Frozen when publishing survey

Survey123 Connect Frozen when publishing survey

Survey123 Connect Settings namespaces field

Re: Understanding Survey123's custom URL Scheme

Explorer Markup to Field Maps Markup

Re: Constraint: No Line Feed