Latest Contributions by BKS

Hello @ChristopherCounsell , Thanks for the reminder to use Once().  I've used this before but forgot about it. BTW, the reason I use my own editor tracking fields (as well as the ESRI fields) is that if / when I need to make  a structural or content update to the feature service, it auto updates (by nature) the last editor tracking field.  This removes my history of last editor data so I have to update it with my own last editor field. Cheers, @BKS   ... View more

I have done almost exactly what @HélèneTouyéras describes in her use case.  This would be very beneficial to have and it doesn't *seem* that it would be that difficult to implement.  The value of consistency in the UI's is underrated for the UX. BKS ... View more

Thanks again to you both @abureaux and @jcarlson . I will try the remaining suggestion to avoid the 2 repeat recs being created if zero exist the first time and get back.  RE: other two points, thanks for the confirmation info. Your help is most appreciated. BKS ... View more

Hello @jcarlson and @abureaux and thanks for all your help ! I tried to get either, and even a combination, of your solutions to work for me but I kept getting strange results.  I almost gave up and then I tried this solution: 1) Added once(count(${test_rpt})+1) to the repeat_count column of begin repeat record 2) Added allowAdds=true allowUpdates=false query to the bind::esri:parameters column of begin repeat record   This solution produced the following: 1) After loading the survey from the INBOX, 1 additional repeat record (editable since allowAdds=true), was added. 2) It also loads any previous repeat records (read-only since allowUpdates=false query) 3) If I try to save the survey it notifies that I have a required field in the editable repeat record; which is correct. 4) After populating this one and only required field in the repeat, I am able to submit the survey This creates no blank repeat recs and also allows me to have required fields in the repeat.   I've tested this but not exhaustively.  I wonder if there is something you would expect to find given this solution (that perhaps I have not yet found)?   One thing I noticed that is odd (and I cannot explain) is that IF the parent record has zero associated repeat recs, it automatically creates 2 repeat records the first time.  BUT after at least one repeat records exists for a given parent record, it only creates 1 additional repeat record when opening. The other smallish thing is that the repeat that is displayed when the survey is opened is the first repeat created, followed by the next and so on.  To get to the repeat that the user needs to update, they have to click through as many repeat recs as exist.   I realize they can long click on the right arrow to go to the end of the repeat collection, but this is not obvious.  I'm hoping that there might be a way to use position(..) and/or index to have the survey open to the last (most recent) repeat record. Finally one other small thing that I do not understand, is that the user is NOT able to delete the newly created repeat record even though the allowAdds=true.  This I'm quite happy about but wasn't expecting it. Thanks again and I look forward to any further input / advice you might have. Cheers, BKS ... View more

Thanks for that idea @jcarlson . Exactly when does the new repeat record in the 2nd nested repeat (i.e. the Edit Log) get created, when I increment the repeat count by 1?  By doing so you think a new repeat record would be created? Ideally I'd like to create the Edit Log row when any RW value has been changed by the user in the form, BUT as a perhaps simpler alternative, is there a way to create this record as soon as I open the form if I'm doing so to Edit it ?  Just searching for a reasonable solution; doesn't have to be perfect.  However, it would be nice to have something better than relying on the user to add a repeat record and record the change they made. Your assistance is appreciated. BKS ... View more

Hello @ClaudiaK and @BrentKinal1 , I realize your post was several years old but I'm having an issue that conflicts with what you are saying above. I'm using s123 website to view the data but the column headings in the table are NOT the labels but instead the name field for the question.  On the other hand, the filter uses the label value so it's quite confusing to the user.  Finally when we export the data, it uses the name field for column headings. I need to make this consistent so I tried the bind::esri:fieldAlias option mentioned and it did nothing to the table headings.   Have you experienced what I'm experiencing and do you have any work-around to make the filter column names consistent with the table column names? thanks kindly, BKS ... View more

@IsmaelChivite , had a feeling you might say that.  Thx, BKS ... View more

@ZacharySutherby   Just confirmed that when I force it to List mode, it asks me to download it locally. ... View more

@ZacharySutherby perhaps I've confused you.   Currently I have all four FL pop-ups set to Auto mode.  Two of them display the photo inline (i.e. see popupAutoAndGallery_asDesired.png attached), which I presume to be Gallery mode, and two of the FL's display them in a List-like fashion (i.e. see popupAutoAndGallery.png attached). When I click on the inline photo's (per popupAutoAndGallery_asDesired.png), a new tab is opened with the photo/jpg displayed. When I click on the List-like photo's (per popupAutoAndGallery.png), I am asked to download the photo locally.  After doing so, it does not open the downloaded file into a new tab automatically. I believe based on my testing thus far, when I've tried to force it to use List mode, it does the same thing.  Asks me to download it locally. Thanks for any help! ... View more