Latest Contributions by PhilipQueen

‎07-10-2019

Thanks for the quick response Phil. Let me know your email and I can send you the xlsx. As a warning, it is quite large. Philip

‎07-09-2019

I had some weird behavior using the new update of S123 last night. Both a coworker and I were unable to submit a survey when a specific relevant chain is enacted. Specifically, when trying to submit the survey we both got Required Messages for a Note question which is not Required in the Survey. Since the question is a Note, there was no way for us to answer the value and submit the survey. This issue began last week with the new Update (we had submitted the survey in this configuration ~40 times before without issue).It does not extend to other Note fields in the survey. Every field in the survey does have a Required Message, but this is the only question we have found where it is presented without being marked as required.

‎07-02-2019

Great news! This a very robust update. I can't wait to see the polygon and polyline functionality, I hope it truly does make it into the next release.

‎05-23-2019

Thanks for the response Dan, The information in your blog post that when using Excel to Table, blank cells in numeric fields are translated "properly" (I assume this means as blank) is the kind of information I'm looking for - although neither the fields in the Excel or in the FC are numeric. What I'm interested in is why some fields are transferred <Null> and others empty. As to the rest of the response, it does matter that the responses are <Null> (and not some other value essentially meaning null) since the client has a backend process running on the data that allow <Null> values but not empty ones. It doesn't matter that the fields lack data, just what form the lacking data takes. I can always add this in by hand, but its much more efficient for me to set up the process to do it automatically - this saves me time, but more importantly is a QA step to deliver data properly.

‎05-22-2019

Hello, I have an ongoing project that involves taking a table of Northing and Easting values, along with attributes, from a survey team and converting them to GIS points. To do this efficiently, I've formatted an Excel doc to match the fields of my Feature Classes, and when I get a new excel I run it through Excel to Table, Display X,Y for the Table, and then copy and paste from the resulting event layer into the corresponding Feature Class. All of the filled out attributes get transferred over without requiring manual entry, which is quite nice. My issue comes with attributes that are not filled in. For some fields these come in as empty, and for others they come in as <Null>. There are two fields where it is important that they be <Null> and not empty, but these consistently come in as empty. I can't find any logic as to what is different, either in the Excel or the Feature Class, between the fields which come in in two different ways. I would like to be able to set up the Excel to ensure these two fields are converted to <Null>, without either me or the survey team having to input these <Null> values manually. Does anyone have leads on how I can do this? Thanks!

‎03-06-2019

Hey Darryl, You're right, it isn't an option. I tried some likely candidates like {sum} to see if there was something hidden, but with no luck. I don't even see adding calculations as an "Idea" - but I think it's a good candidate for one, as this seems like a real limitation. Sorry I couldn't be of more help, Philip

‎02-27-2019

James, Thanks for following up on this, it's good to know that multiple layer views cause this setting. I was able to correctly diagnose what went wrong in our case. We had created our views with a script that set "Source Schema Changes Allowed" to false and locked our schema. This property for the hosted feature layer is calculated from all of the view layers, so if one view layer has it set to false you can't change your schema. This explained why we initially couldn't change the property in our hosted feature later through REST. But we also couldn't change the property to true in any of the view layers through REST, until Khaled Hassen told us that 'hasStaticData' has to be set to the opposite boolean value as "Source Schema Changes Allowed" - so to change the latter to true you have to set the former to false at the same time for the update to take. So we were able to make all of the changes and then add the fields we needed. Hopefully typing this all out here helps someone solve this issue a little quicker than it took our team. Thanks again James.

‎02-26-2019

Rawand, I haven't used now() or today() commands much before, but maybe the once() command could solve this issue? The evaluation of time commands is explained a bit here: https://docs.opendatakit.org/form-logic/#form-logic-gotchas Hope that helps, Philip

‎02-21-2019

In addition to what Jay Johnson‌ said above, it could be a good idea to move some of that guidance into the survey. You could insert a note at the top of your survey with the text of the last sentence, which is mainly information for filling out the survey correctly, not information about the survey. If it's very important, you could even force the user to click a "I've read and understood the text above" button before proceeding to the rest of the survey. This may be a case where documentation should be done in a separate document alongside the metadata. It does look like a bug in the Survey123 app though!

‎02-21-2019

I'm not sure why republishing an old survey would work better than a new one, but I'm glad it worked out!

Online Status	Offline
Date Last Visited	‎11-11-2020 02:24 AM

My Ideas

Latest Contributions by PhilipQueen

Re: World UFO Day Release (3.5)

Re: World UFO Day Release (3.5)

Re: World UFO Day Release (3.5)

Re: Excel to Table - Null vs. Empty Values

Excel to Table - Null vs. Empty Values

Re: Calc percentage in Operations Dashboard?

Re: Can Views Cause Error 400: Unable to Add Feature Service Layer Definition?

Re: time changes with repeat

Re: Too much Metadata could be a bad thing!

Re: Combine 2 surveys