Latest Contributions by NicholasMoore

‎04-23-2024

It is often required to have a unique id that is not a gloablid structure in reports so they can be linked to the service data and all other aspects of the information model that is semi human readible. Objectid is always created against the layers but you are unable to use the ObjectID field in Feature report templates. It would be great if we could expose the Objectid and other system generated fields not created through Survey123 Connect or web designer to the FRTs @JamesTedrick

‎06-28-2021

In our workflows we often require multiple Survey123 forms. Many of the forms are setup purely as web based forms and are not required in the field or were not designed to be used in the field (many are duplicates of the field versions and integrated in dashboards for reviewing the data - with cut down functionality and web based enhancements) It would be great if we could flag these Forms as web app only (much like you can flag a web map as usable in collector). This would eliminate many unnecessary forms popping up in the field apps for download that were never intended for the field app @IsmaelChivite @JamesTedrick

‎06-28-2021

@JodyZhengLiu @IsmaelChivite @JamesTedrick We are also experiencing the same behaviour with orderbyfields within a nested repeat. Grandparent > Parent > Child We have tested numerous iterations and what seems to be happening as soon as you apply an orderbyfields to the nested repeat table (Child), it returns all records from the Child associated through the parent but at the Grand Parent level. i.e. not filtering to the relevant Parent. Thus in the FRT report the parent shows all child records regardless of relationship to the parent. Data example here Site (Grandparent) - siteid: AB1 Strata (Parent) - strata: T Specie (Child) specie: acacia Specie (Child) specie: xyz Strata (Parent) - strata: G Specie (Child) specie: abc Specie (Child) specie: def The FRT Report with orderbyfield on species does this (note sorted) Site (Grandparent) - siteid: AB1 Strata (Parent) - strata: T Specie (Child) specie: abc Specie (Child) specie: acacia Specie (Child) specie: def Specie (Child) specie: xyz Strata (Parent) - strata: G Specie (Child) specie: abc Specie (Child) specie: acacia Specie (Child) specie: def Specie (Child) specie: xyz We think this is a bug within the FRT and order by in the nested repeats Regards Nick

‎02-28-2021

Hi @CooperLogan , Do you have any bug reports regarding the GlobalID/GUID issue with related reports. I have also hit this stumbling block?

‎11-03-2020

Ismael Chivite‌ We have a survey with a repeat section. The repeat table has hyphens in its naming convention. Similar to PRJ-12345-DD-inspections. We have a series of cascading selects within this repeat table. one select_one question and another with with a choice filter for example utilising this country=${country} convention. When the table name has hyphens in it, we are experiencing an issue that the choice_filter does not work, it does seem to work if we rename the repeat table. This seems to not be documented anywhere? Is this something you have come across before? can you confirm if this is a bug?

‎10-28-2020

James, Thanks for the quick response. Both Cameron Irvine‌ and I have discussed and non of those limitations apply to either of those two deployments. Would there be anything else we could look into?

‎10-28-2020

Ismael Chivite , James Tedrick and Team We have been trying to debug feature report templates together with our Portal Administrator Cameron Irvine‌. We have two new portals on 10.8.1 - We have published some basic surveys (a geopoint and a single question as well as some advanced surveys with nested repeats etc) utilising Survey123 Connect. We have attempted to generate feature report templates with maps however every time we include a geopoint question in the feature report template we get "Failed to print map for ${insp_location}. Error: Failed to load web map: Failed to load portal item" .We have tested the following: A default sample template with geopoint as default ${insp_location} A default sample template with geopoint as ${insp_location | mapSettings:" bc4c39e14d3b46549e8b0a53f3be144e":100000} - Where the map has world imagery and the geopoint only A template with no geopoint - this generates fine We have tested with a form to a custom submission url to hosted feature services and also services generated by enterprise - This does not make a difference. It is not survey dependent and is happening with all surveys and all web maps The surveys do not use tile layers as is suggested by this post (Error: Failed to print map for ${}. Failed to load web map: Failed to load portal item ) We have an older portal where the feature report templates all work fine however the new portals are returning these issues. To us it is as if a cross domain request from the Survey123 website for a portal item is getting blocked by the portal, but there is no visibility of this. Is there anything we can look into or do you have suggestion to get this working? We would appreciate any direction we can get? Regards Nick

‎09-28-2020

Is there a way of escalating this John Plunkett its one of the things that is negating a full migration from Desktop to Pro. Dave McPherson, Cameron Irvine

‎09-28-2020

100% agree and this is what i was hoping to achieve through this idea

‎09-28-2020

As per Felicity chun‌ post. changing the user environment variable Home you can redirect all surveys to anywhere you want

‎04-29-2020

John, Could you please update us on the status of this request? Regards Nick

‎07-08-2019

James, I am assuming this also applies to Portal for ArcGIS? And are there any workarounds to this that you know of?

‎05-19-2019

John, Has there been any update on this. Do you know? Its seems more than a year now and we still waiting on a response. Regards, Nick

‎07-22-2018

Thanks for the response David. At the moment the current elements that do not fit the standard families in our file throw the error as described above. It would be good to capture these even if they come across into the Generic Model for now, until, Esri have found away to read all families in.

‎07-19-2018

Hi There, We have been testing the new functionality with ArcGIS Pro 2.2 and have found that it does not read all Revit files even though they are in 2018 format. Does ArcGIS Pro only read "standard" families and what are the limitations there? Any revit file that has MEP Fabrication Pipework Families will not open in pro. These are created using the Autodesk Fabrication Piping Plugin. This would also mean that Fabrication Ducting and HVAC systems created through the same plugin will not actually work. When i open the Revit file, remove these pipes and fittings from the model it opens fine. The error thrown by Pro is as Follows: "External Component has thrown an Exception" No Error Code. Any help would be much appreciated?

Online Status	Offline
Date Last Visited	‎04-29-2024 07:15 AM

My Ideas

Latest Contributions by NicholasMoore

Expose ObjectID field to Feature Report Templates

Mark Survey123 as Webform only

Re: Feature Reports orderByFields syntax

Re: Why don't photo attachments show up in reports created in ArcGIS Pro?

Re: Survey123 Tricks of the Trade: Choice Filters

Re: Feature Report Template failing to load web map: failed to load portal item

Feature Report Template failing to load web map: failed to load portal item

Re: overlay route events in arcGIS Pro

Re: Standardise Standard editor tracking fields between Esri Products

Re: Survey123 ability to have survey stored on a network drive

Re: overlay route events in arcGIS Pro

Re: Survey123 Export Report Photos not showing

Re: overlay route events in arcGIS Pro

Re: ArcGIS Pro 2.2 - REVIT Files with families from plugins

ArcGIS Pro 2.2 - REVIT Files with families from plugins

Expose ObjectID field to Feature Report Templates

Mark Survey123 as Webform only

Re: Feature Reports orderByFields syntax

Feature Report Template failing to load web map: f...

Standardise Standard editor tracking fields betwee...