I have services running for our town that represent town parcels for our interactive mapping website. Internally and for private use this parcel layer (let's call is Parcel 1) contains roll number, owner name, address, and various other fields. We have another layer that is basically just a copy of Parcel 1 but is for public use. This layer contains all the same fields except for the owner information (Parcel 2). What I have done is basically copied Parcel 1 and deleted the unnecessary fields for Parcel 2.
When changes are made to Parcel 1, I delete Parcel 2, export/copy Parcel 1 and rename it to Parcel 2 (or simple edit the geometry and information in Parcel 2 to reflect changes in Parcel 1...essentially making the same edits twice.)
What I want to know is, is this the most efficient workflow?
What I want is for when changes are made to Parcel 1 for Parcel 2 to automatically update it's geometry and fields at the same time.
Is this possible since there is different schema?
I have replicas running on these feature classes so add/deleting a feature class proves to be quite a pain.
The comments below to create separate services with fields hidden seems to work fine. The answer for creating an additional replica for Parcels also seems feasible. The problem I'm encountering now is that the parcel data is bad quality. We receive a lot of our information from a tax database and another source and the road names are not correct or contain different alias. What I did was create a a copy of the parcels and renamed the roads so that a query/search by the user would yield a result. As a work around. I'm uncertain how to proceed. A replica with the street name field I created (different from Parcel1) could feasibly work so that the original street name isn't synced. However, new parcels that are added would then not be synchronized correctly.
Any thoughts on this issue?