topic Re: Assign Default to Field when using Branched Versioning in ArcGIS Parcel Fabric Questions

Assign Default to Field when using Branched Versioning

DeanAnderson2 — Sun, 26 Jun 2022 12:59:06 GMT

We are in the process of testing branched versioning with Parcel Fabric. I preparation we have using parcel fabric in a standard Geodatabase. The AssignDefaultToField tool appears to work fine in ParcelFabric editing of a feature in a geodatabase. However, it does not appear to work in when using branched versioning. Using standard processes I can go in and change a default value (see below)

However, when I go to use the tool it give the following error message.

From the documentation it does not appear that this should be a problem. Is this an error or did I miss something regarding the limitation of features stored in a branched version?

Re: Assign Default to Field when using Branched Versioning

AmirBar-Maor — Mon, 27 Jun 2022 07:50:08 GMT

@DeanAnderson2

Since the parcel fabric controls simple feature classes this has nothing to do with the parcel fabric.

When using web services, changing the schema is not done through the 'layer' but through the 'feature class'. This means you have to connect to the database as the 'data owner' and drag the the 'feature class' to the geoprocessing tool.

Another way to assign a default value is to use the data design view:

Just make sure to first stop the service, then modify the schema, then restart the service.

In the fields data design view you can change any field property that is stored in the 'layer' like which field to highlight. Such changes do not require stopping and restarting the service.

Re: Assign Default to Field when using Branched Versioning

DeanAnderson2 — Mon, 22 Aug 2022 17:59:26 GMT

Amir

Thanks for the response and I apologize for my slow response (as usual). I get it that the tool changes the schema. What I would like is a tool that does NOT to change the schema but lets me replicate what I can currently do interactively from within the CreateFeatures / Active Template tab. Using the tab I can open the active template and change set the default for the features I am about to create.

This default is assigned for the features I am going to add. When that is done the "default" gets reset back to schema.

Having this capability to programmatically set the default would be nice. I hope this clarifies what I am trying to do.

Thanks