Latest Contributions by Jim-Moore

Hi @FaresAl two new functions were introduced in Connect 3.12 (2021) for working with repeat indexes: position(..) and indexed-repeat(). Please refer to the following documentation: Return the index of a repeat record Use values from indexed repeats ... View more

Hi @AirX  You can display each repeat record on a new page by adding a page break inside the repeat block. For example:   ${#my_repeat} ${first_question_in_repeat} ${second_question_in_repeat} ...etc... ${last_question_in_repeat} <Page break goes here> ${/} <Repeat's closing tag will be on the first line of the next page of the template>   Hope this helps. Best, Jim cc: @RuthJiatengXu  ... View more

Hi @JackTsai  Are you publishing a new survey from Survey123 Connect or updating an existing one? If it's the latter, you might need to add version=latest to the URL to ensure you're using the latest version of the web app. Could you please try publishing a new survey from Connect with a multiline image question and see if it works in the web? Please note the latest version of Survey123 Connect was released September 2024 and is version 3.21. Best, Jim cc: @JodyZhengLiu  ... View more

Hi @D_AnneHammond  The pulldata("@layer") expression shown above should use the getValue operation, as opposed to getValueAt. The distinction is that getValueAt requires a geopoint so that it can query the feature layer "at" a particular location; whereas getValue uses a WHERE clause to filter the features by attribute (in this case, filter on MapTaxlot and return its polygon). Could you please try changing to getValue and see if that helps? Jim   ... View more

Hi @D_AnneHammond  Thanks for sharing your XLSForm. In the calculation for the geoshape question: pulldata("@layer", "getRecordAt","<url>","MapTaxlot=${MapTaxlot}") This should use the getValue operation to retrieve the geometry of the tax lot. The WHERE clause also needs to include quotes around the value. So something like this: pulldata("@layer", "getValue", "geometry", "<url>", concat("MapTaxlot='", ${MapTaxlot}, "'")) Check out the Query a Feature Layer sample in Survey123 Connect for some useful pulldata("@layer") examples. Regarding the zoning and idrzone questions, unfortunately the calculations for these will throw an error because they're attempting a polygon-in-polygon query; the getRecordAt and getValueAt operations require a geopoint as input (i.e. point-in-polygon query). Hope this helps, Jim ... View more

Hi @MollyMoore  The syntax in your expressions looks good. A couple of things to check: Is "site_name" the exact name of the field in the feature layer with which you want to populate the choice list? Does the signed in user have access to the feature layer? Best, Jim ... View more

Hi @DfIRivers  You should now see the correct video at - ArcGIS Survey123: Modeling Inspection Workflows - Esri Videos: GIS, Events, ArcGIS Products & Industries Best, Jim ... View more

Hi @DfIRivers  Thanks for reporting this! I've contacted the team that looks after this content to get the video updated. In the meantime - here's an older version of a similar presentation, also presented by @IsmaelChivite . Even though this one is from the 2022 User Conference, much of the content is still current. ArcGIS Survey123: Modeling Inspection Workflows - Esri Videos: GIS, Events, ArcGIS Products & Industries Best, Jim ... View more

Hi @NateExley  Your syntax is very close. There are two operations you can use with pulldata("@layer") to query a layer by location. These are getRecordAt and getValueAt. The distinction is that getRecordAt returns the whole record as JSON (that is, all attributes for the first match the query gets); so you would need to use one or more subsequent pulldata("@json") calculations to retrieve the exact values you want. On the other hand, getValueAt allows you to skip the pulldata("@json") step and get straight to the exact attribute you want.  So getRecordAt is useful if you want to run the query once, but retrieve multiple attributes; whereas getValueAt is useful if you just want to retrieve a single attribute. In your case, if you want to retrieve both the building name and room number from a record in the same layer, you could either: Run pulldata("@layer") with a getRecordAt operation, then use two pulldata("@json") calculations, one for each value; or Run two pulldata("@layer") calculations with a getValueAt operation - one calculation for each value. The difference is, with option 2 you're running two queries against the feature layer, whereas with option 1 you're only doing the query once.  Note the syntax is slightly different for getValueAt because you also have to supply the attribute you want. This blog post has heaps of useful tips. The Query a feature layer section of the documentation has lots of great information too. Hope this helps, Jim ... View more

Hi @AlexFazzino two new functions were introduced in Connect 3.12 (2021) for working with repeat indexes: position(..) and indexed-repeat(). Please refer to the following documentation: Return the index of a repeat record Use values from indexed repeats ... View more

Hi @ModernElectric  Sorry for any confusion. If there's no WHERE clause in the expression, the pulldata("@layer") query defaults to a WHERE of "1=1" (i.e. return all records without any filtering) and will return the first record from the query results (see the Query a feature layer documentation). So removing the WHERE clause should at least confirm if Survey123 can successfully query the feature layer and get a result.  Perhaps give that a try first and if you get no result, check: that the URL is correct; that the feature layer is shared appropriately; and (in the case of a getValue request) that the attribute you're trying to retrieve matches the field name in the feature layer. Once you confirm that the feature layer can be queried successfully, you can work out why there's no match happening with the WHERE clause. ... View more

@ModernElectric the syntax in your XLSForm looks good to me. It's a bit tricky to diagnose without the feature layer, but everything seems to be set up correctly. Is the autocomplete search() working for the inventory descriptions? If you drop the WHERE clause from the pulldata("@layer") expressions, do you get a result?   ... View more

Hi @ModernElectric  I'm guessing the quotes (") in the DESCRIPTION field values are causing an issue with the WHERE clause. Try enclosing the value for the WHERE clause in single quotes, e.g.  concat("DESCRIPTION='", ${Description_1}, "'") Hope this helps, Jim cc: @ZacharySutherby  ... View more