For internal workflows, we have gigabytes of utility asset photos in our enterprise data. When we publish user-managed services, we do not explicitly include attachments - they come automatically. That means that if we have more than 1GB of attachments in a service, we are unable to share that service as a copy through the distributed collaboration. We do not need or want the photos to go through the collaboration because our ArcGIS Online organization is for public-facing maps and apps.
My idea is to either:
- Create a way to publish a user-managed service with a registered enterprise geodatabase and explicitly exclude attachments from the service, or
- Provide a setting in the distributed collaboration that allows us to exclude attachments from copies. Ideally, this option would give the user the option to include/exclude attachments at the service level, but having that setting at the workspace level would be an acceptable alternative as long as a Portal-AGO collaboration can have more than one workspace.
