Community

All Communities

Products

ArcGIS Pro ArcGIS Survey123 ArcGIS Online ArcGIS Enterprise Data Management Geoprocessing ArcGIS Web AppBuilder ArcGIS Experience Builder ArcGIS Dashboards ArcGIS CityEngine ArcGIS Spatial Analyst All Products Communities

Industries

Education Water Resources State & Local Government Transportation Gas and Pipeline Water Utilities Roads and Highways Telecommunications Natural Resources Electric Public Safety All Industries Communities

Developers

Python JavaScript Maps SDK Native Maps SDKs ArcGIS API for Python ArcObjects SDK ArcGIS Pro SDK Developers - General ArcGIS REST APIs and Services ArcGIS Online Developers File Geodatabase API Game Engine Maps SDKs All Developers Communities

Worldwide

Comunidad Esri Colombia - Ecuador - Panamá ArcGIS 開発者コミュニティ Czech GIS ArcNesia Esri India GeoDev Germany ArcGIS Content - Esri Nederland Esri Italia Community Comunidad GEOTEC Esri Ireland Používatelia ArcGIS All Worldwide Communities

All Communities

Products Developers User Groups Industries Services Community Resources Worldwide Events Learning ArcGIS Topics Networks View All Communities
ArcGIS Ideas
GIS Life
Community Resources

Community Help Documents

Community Blog

Community Feedback

Member Introductions

Community Ideas

All Community Resources

New Contributor

since

5 Badges Earned

‎02-08-2024

1 Posts created

1 Kudos given

0 Solutions

0 Kudos received

My Ideas

(0 Idea Submissions)

Show:

Status:

Latest Contributions by GroundsAdmin

POST

I would have to agree with Dominick- the lack of continuous collect for related tables negates the efficiency they provide. I've had to remove all my related tables because it isn't worth my clients time when they are putting in hundreds to thousands of points of data in daily. Continuous collect is imperative for related tables to be a useful feature in mobile data collection.

0

0

551