Possibility to exclude related data copied to server when publishing MapImageServer

[MaximeDemers]

Hello,

I am now using Enterprise 10.9.1 with Pro 2.9.14.

I have noticed a change with the previous version I used, Enterprise 10.6.1 with Pro 2.7, when data are copied to the server when publishing a MapImageServer.

Since the upgrade, it seems all the related data to any layer in an aprx is also copied to the server even if they are not included in the map.

In my situation, this is not a good thing because a particular layer is related to 6 other feature classes that have attachments enabled, resulting in 3.6 GB being copied to the server instead of 80 MB before. Moreover, this layer is used in many other MapImageLayer so the unwanted attachments are duplicated on the server many times for nothing.

It would be really interesting to have the option to exclude unwanted related data when publishing a MapImageServer.

Thank you

[KathleenCSki]

As a work around, before publishing you could move a copy of the data for the feature with the complex relationships into a feature without relationships.

[MaximeDemers]

Hi @KathleenCSki

Thank you for your suggestion.

I know there is workarounds for this issue. Making a copy of the feature class without the relation class is probably the best as you suggest. However we are using scripting for publishing services in an automatic and scheduled way in order to keep services up to date. Adding the need to make a copy of each such feature class is not optimal.

I still think there should be an option to opt out the copy of uneeded related data at the publishing stage.