Latest Contributions by DougBrowning

Can this be added though?  Or stop them right away before moving on.  It has been a big issue for users.  Esp since every other forms program we have used did this. I know some of these are bugs but it really should be able to bring you right to the problem.  Imagine buying something online and when filling out the form it just said "missing data error" but did not bring to say your missing first name.  It is just expected now. Thanks!! ... View more

I had this problem in windows also.  You can install not as admin, but if you do, it seems that the program associations never get set - so windows has no idea.  That said I have not had much luck ever getting windows to work. ... View more

Try binding the field using the  bind::esri:fieldType column. ... View more

Found it.  We are both right. Note that this is the url to the feature layer item, rather than the url of the feature service itslef.  In old versions of Survey123 we actually supported working directly with feature service urls, but when you let Survey123 Connect create your initial XLSForm design, the feature layer item url will always be used.  Right now, Survey123 supports feature service urls only for backwards compatibility. you should always use a url to the item! What is weird is there is no easy way to get the URL that uses itemid.  How does survey123 expect you to get this URL? If I go to the Rest page and look for the Service ItemId: then I can find the item id.   Then I have to know to use this start https://www.arcgis.com/sharing/rest/content/items/  and add that item id on at the end. When you try and look at this URL I just get a blank page with API reference on it - which makes it seem wrong. Is there a easier way to get this url?  When you do to the Item page of the service at the bottom it says URL and gives the /FeatureServer one. So it would make sense that is what you want.  Old way seemed a lot easier and less confusing. For the poster I think it is this  Never use the Token that is just to get in for security https://www.arcgis.com/sharing/rest/content/items/988dddec82b9478ab2a89ac32058adb9 ... View more

Is this a new change?  I have been using the /FeatureServer for years and it works just fine. ... View more

Opps I was writing Ifs all day so I forgot.  Same though - evaluate to true. How I use if in relevant is things like if(${state}="WA",${Type_Suivi}='Elimination',0).  This is having a relevant only for certain situations. Sorry about that ... View more

The statement must evaluate to True not 'yes'.  You can pull this off using 1 and 0. Use this  if (${Type_Suivi}='Elimination',1,0) ... View more

Yea my field season starts May 6 and users/me are freaking out a bit.  It is just so confusing to the users when errors get caught at random times.  Note I also see it not always triggering when leaving a field which is supposed to work.  They keep telling me to fix it and I keep having to say I cannot. I hope 123 starts to get that most field work is season based.  This may mean adjusting the release timing.  Not just to get it out before the season starts but also to NOT release during.  I know a number of people who had working forms break during the season due to app updates.  I wish I could lock this down somehow. Good idea on checking for empty at the end.  ( Not much help for constraints though. ) Not sure how I could get that across 50-100 repeats though.  I could maybe figure out there is one but not which one.   Hopefully this will add to its importance to get fixed.  I have been surprised no one else has noticed the issue. ... View more

Does the field have a relevant on it?  Phil and I traced down this error already.   When a field has a relevant and a constraint or required it is not triggering the message sometimes.  For me fields will no relevant trigger a message when going to the next repeat.  When a field has a relevant (and not showing on initial repeat load) it will not check the constraint and message until the form is submitted.  Which with 50 repeats is a huge mess (they must now hit submit 50+ times!).  I have now also found some fields that never check the required and let it send even with the broken rule.  These may be a relevant, constraint, required combo that messes it up.  This sounds like what you have. I went back and forth with Phil on this and he said it is now a know bug and set to be fixed in the next release.  He said these relevant, constraints thing was completely overhauled in 3.3.  And they did not get it right. I really hope it gets fixed soon as this is delaying my field season with hundreds of people. Hope that helps ... View more

So, GroupOwnerUser tries to invite User_AB to OrgAGroup, is that right?       - Correct Does GroupOwnerUser have to be User_A or it can be anyone?    - If GroupOwnerUser is User_A then it will skip User_A and find User_AB no problem.      - If GroupOwnerUser is NOT User_A then User_AB will never be found. Note in my org it is just how I wrote it with the _ so test that also.  AKA user_A and user_A_B.  This may cause a difference. Thanks! ... View more

You should not have the /0 in there.  Just end with FeatureServer.  Also no token at the end of course. So  this  https://services7.arcgis.com/S7DHOirgbYgdtrbR/arcgis/rest/services/survey123_536269680eb04998a5baf980af0623a1/FeatureServer Then you set form_id (also in settings) which is used to find the right layer instead of the /0.  So your /0 layer is called surveyPoint.  Put that in form_id. On another not you have some crazy long field names.  I would watch that, could get you. ... View more

Another vote.  Esp for super long lists where a subset is used a lot each day.  Most other form programs attempt to learn user answers over time.  Even moving the last picked item to the top of the list would be a start. ... View more