Latest Contributions by GISAdminGKB

Workaround Save the excel file. THEN BEFORE PUBLISHING: Goto survey files Open de <form>.xml file Replace the % sign with HMTL entity &#37;  Then publish the survey !! See example below, the same search appeance with the % replaced. When we publish this everything works fine. <select1 appearance="autocomplete search(&quot;GKB_Project?url=https://services9.arcgis.com/CjT8oELYhF7fnj6q/arcgis/rest/services/service_e7e8bc459ba240c5a1153dcbc... DESC&amp;where=Projectnummer LIKE 'WHGB&#37;' AND UPPER(Omschrijving) LIKE '&#37;ROLDEUR&#37;'&quot;) w3" esri:style="&lt;body backgroundColor='#f8f8f7'&gt;" ref="/Deurinspecties/LocatieGegevens/ProjectCode"> <label>Projectcode</label> <hint><output value=" /Deurinspecties/LocatieGegevens/ProjectOmschrijving "/></hint> <item> <label>Projectnummer</label> <value>Projectnummer</value> </item> </select1> ... View more

Workaround Save the excel file. Goto survey files Open de <form>.xml file Replace the % sign with HMTL entity &#37;  See example below, the same search appeance with the % replaced. When we publish this everything works fine. <select1 appearance="autocomplete search(&quot;GKB_Project?url=https://services9.arcgis.com/CjT8oELYhF7fnj6q/arcgis/rest/services/service_e7e8bc459ba240c5a1153dcbc40c33d2/FeatureServer/0&amp;orderByFields=Projectnummer DESC&amp;where=Projectnummer LIKE 'WHGB&#37;' AND UPPER(Omschrijving) LIKE '&#37;ROLDEUR&#37;'&quot;) w3" esri:style="&lt;body backgroundColor='#f8f8f7'&gt;" ref="/Deurinspecties/LocatieGegevens/ProjectCode"> <label>Projectcode</label> <hint><output value=" /Deurinspecties/LocatieGegevens/ProjectOmschrijving "/></hint> <item> <label>Projectnummer</label> <value>Projectnummer</value> </item> </select1> ... View more

We had the same problem. Developing a (submission) survey, many times publishing and testing the form in survey app. But during development the createReport API start failing and we got the message as mentioned above. We did some testing. Finally we found the reason. In one field we are using the search appearance and when we use the % sign in the url+parameters xfom is broken for analyse and data and alos the createReport API. So we had search appearance like this:  autocomplete search("GKB_Project?url=https://services9.arcgis.com/CjT8oELYhF7fnj6q/arcgis/rest/services/service_e7e8bc459ba240c5a1153dcbc40c33d2/FeatureServer/0&orderByFields=Projectnummer DESC&where=Projectnummer LIKE 'WHGB%' AND UPPER(Omschrijving) LIKE '%ROLDEUR%'") w3 Using as above xform is broken, removing the % sign everything works fine. Tomorrow we will make a support ticket about this. Maybe is it's helping others to solve the message ' Cannot get necessary XForms file for the survey. ... View more

We had the same problem since last week. But we could solve it by setting the coordinate system in the environments tab of the tool. However we never had to do this before. ... View more

Hi Ismaël, Great video;s, very interesting. But where can we find the scripts as explained in the videos like the one by James Tedrick about updating attachment keywords ? It would be very helpfull if we can get these samples somewhere.   Kind regards from Holland, Dirk-Jan ... View more

Yes. We did some investigation and were able to do. Although in this way it's not respecting the relation. But according to the documentation the syntax for statistics/summary is ${layerName | stats:"outStatistics":"groupByFieldsForStatistics":"havingClause"} For LayerName you can use each layer within the hosted layer. Creating and publishing a survey with repeats will create a hosted layer with mulitple layers. Each repeat will be a layer (a table) within the hosted layer. For example. The hydrants has a repeat for the inspections. In the report you can have: ${Hydrants | stats:"count,OJBECT_ID"} (the number of hydrants) ${Inspections | stats:"count,OJBECT_ID"} (the total number of inspections)   IMPORTANT: the relation between e.g. the hydrants and inspections is not taken into account. You can do it yourselves using the WHERE clausule in de syntax. In our repeats we always have a number of fields from the parentlayer to be able to report indepently from the parentlayer. We use this fields for grouping and selecting. ... View more

Hi, What about statistics, summary and repeats (related tables). Is it possible to use stats on related tables ? In our case, using forms to collect data, most of the information is stored in the related tables (repeats) ?? However, we like all of the (coming soon) new reporting and other new features in survey123 connect and fieldapp  ... View more