Hi guys,
im working on a data loading workbench for our sql sde database.
when applying change detection before writting into database, is there a way it can be dynamic and detect changes in group? Like original dataset a comparing to update dataset a, and b to b with key and compare field listed in a sheet?
Thanks guys!
Yes. Use any Group ID Attribute as another selected compare attribute in the Update Detection Key Attributes Parameter. This way say Group: A ; ID:1 will be compared directly with a corresponding feature that is also Group:A ; ID:1
Yes. Use any Group ID Attribute as another selected compare attribute in the Update Detection Key Attributes Parameter. This way say Group: A ; ID:1 will be compared directly with a corresponding feature that is also Group:A ; ID:1
Thanks bwn.
I’m stuck at here... Since im using a list to read multiple feature classes from SDE and downloaded file gdb., i am unable to select the filed name i need to use to compare… any suggestion how i can “expose” all these field? i cannot see a way to get the change detector to read from a list...
Thanks!
At a minimum, in the FeatureReaders you will need to Expose the Key Attribute(s). Curently they are not set to do this and only have the Feature Class name exposed, and so this makes it not possible to compare features without the Key Attribute(s) names exposed to the workspace.
Within the FeatureReaders change the Parameter “Attributes to Expose“ to include the names of the Key Attribute fields.
If you are comparing multiple Feature Classes at once, and they have different names for their Key Attributes, I would use an AttributeCreator to create a commonly named Key Attributes like “Key” and/or “Group” to use in ChangeDetector to make it so that it can compare multiple FCs at once by setting “Update Detection Key Attributes” to FCName, Key or FCName, Group, Key etc.
In terms of Attribute comparison settings, then there are two choices when using FeatureReaders with dynamic reading like this. “Dynamic” reading means that you have set them to not know in advance what the Attribute Names will be output.
Option 1 is to use some sample Feature Classes to set the “Attributes to Expose” parameter within the FeatureReaders with ALL the names of the feature class fields. This can be “taught” to the FeatureReader by using the “Import” function within “Attributes to Expose”. Then you will have those Attribute Names available to the workspace, including within ChangeDetector.
Option 2 is to leave the other Attributes unexposed (except for the Key and Group attributes). However in this case ChangeDetector must be set with “Match All Except Selected Attributes“ with the Key Attributes selected.
At a minimum, in the FeatureReaders you will need to Expose the Key Attribute(s). Curently they are not set to do this and only have the Feature Class name exposed, and so this makes it not possible to compare features without the Key Attribute(s) names exposed to the workspace.
Within the FeatureReaders change the Parameter “Attributes to Expose“ to include the names of the Key Attribute fields.
If you are comparing multiple Feature Classes at once, and they have different names for their Key Attributes, I would use an AttributeCreator to create a commonly named Key Attributes like “Key” and/or “Group” to use in ChangeDetector to make it so that it can compare multiple FCs at once by setting “Update Detection Key Attributes” to FCName, Key or FCName, Group, Key etc.
In terms of Attribute comparison settings, then there are two choices when using FeatureReaders with dynamic reading like this. “Dynamic” reading means that you have set them to not know in advance what the Attribute Names will be output.
Option 1 is to use some sample Feature Classes to set the “Attributes to Expose” parameter within the FeatureReaders with ALL the names of the feature class fields. This can be “taught” to the FeatureReader by using the “Import” function within “Attributes to Expose”. Then you will have those Attribute Names available to the workspace, including within ChangeDetector.
Option 2 is to leave the other Attributes unexposed (except for the Key and Group attributes). However in this case ChangeDetector must be set with “Match All Except Selected Attributes“ with the Key Attributes selected.
thanks again mate! i ve used import attribute in this case then manually select the ones to compare.. such a shame it cant use value from a field or a list to get it run dynamically..