Latest Contributions by IsmaelChivite

@MichaelBishopp  It looks like we got lost in translation. This link may be helpful to you: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-saphana/enterprise-geodatabase-limits.htm   ... View more

I am thinking you could create a web map including all the layers and then make the map in your report PDF use that web map. ... View more

I am not sure I completely follow your question here. It seems like you have a signature question in a Survey123 form and you want to create a report in PDF format that includes the signatures collected. The Survey123 report syntax to include a signature in your PDF output would look something like this: ${my_signature_question | size:400:0} The above would take the signature in the question named my_signature_question and represent it as an image of 400 pixels in width. ... View more

@AmberKeller2 @survey123_solutions  Sorry to hear you did not get any email notification. A cancellation email was sent on Monday April 24 to everyone who registered. I wonder if the email was quarantined by your spam filter?   ... View more

@MichaelBishopp  I agree with @Katie_Clark , you can make Survey123 question labels really long.  Just for fun, today I created a label with 133,000 characters, and it did work fine in both the mobile and web apps. The text is longer anyone would every want to read! 🙂 In practice, what bites you is not the limit on the Survey123 labels, but the limit on the ArcGIS field alias. When you publish a survey, the label of the question is used to populate the field alias. That is where you are going to get errors, while publishing. So here are a few recommendations: Specify the field alias using the bind::esriFieldAlias column in your XLSForm (limit is 255 characters).  Set the bind::esriFieldType value to null (like @Katie_Clark did) If the label belongs to a note question type, do not specify a value in the name column ... View more

  @BrandonA_CDPH  I guess something like this should do: If the user is logged-in, the name and email questions will get automatically populated and hidden. If the user is not logged-in, they will show in the form for the end user to complete.  In this particular case, you will not want to use the relevant column. You will want to use the body::esri:visible column instead.   ... View more

@cyyyn206  I guess one approach you can take is to include a calculation in your Survey123 form so the area is calculated into a Number hidden question. Follow instructions as shown in the animation below:   Later, you will be able to use this numeric field in Experience Builder. ... View more

@GIS_Ecologist  Use arrow symbology for the sketch geometry while the user is interactively entering the bat flight in the geotrace question: Not possible. You can style the line color and width , but cannot add an arrow at the end.  In the geotrace map, use arrows to display all bat flights previously entered: This is possible if you configure your geotrace question to use a custom web map. You will need to add to your web map the bat flights and use arrows for symbology. ... View more

I realize now that you seemed to be asking a different question originally. Sorry for the guessing. To your question: Yes, the pulldata getRecord operation allows you to query date fields. Essentially, any WHERE statement you can pass to a feature layer, is supported in the pulldata getRecord operation. For example: pulldata("@layer","getRecord","<yourlayerURL>","RECDATETIME BETWEEN CURRENT_TIMESTAMP - 7 AND CURRENT_TIMESTAMP") pulldata("@layer","getRecord","<yourlayerURL>","RECDATETIME BETWEEN DATE '2023-04-27' AND DATE '2023-04-29'")   Check the Date and Time format section of this help topic for details on the date queries you can make to an ArcGIS layer: https://developers.arcgis.com/rest/services-reference/enterprise/query-feature-service-layer-.htm  Important consideration: ArcGIS stores date values in UTC. The pulldata() get record operation returns only ONE record.    ... View more

I published your XLSForm using Survey123 Connect version 3.17. Everything worked fine in both the Survey123 Connect preview as well as in the web browser. I do not see why this same XLSForm would fail with previous versions or have an inconsistent behavior across different clients. The XLSForm syntax looks good.  I can't think of anything obvious that would cause a problem. For consistency, try publishing with version 3.17 of Survey123 Connect, if not already, but again, your XLSForm looks good. I wonder if the problem relates to the sharing of the geocode service: What if someone made the geocode service in your organization private? Assuming you are not logged-in in your browser, this could explain why reverse geocode info does not come when you use the web app. ... View more

@JerrySneary  You should be able to. Expressions in the relevant and body::visible columns should work regardless.  ... View more