Is there a bug in the Inspector class that stops a Subtype update on a new record?
I have a custom panel which uses an Inspector embedded control. The Inspector is set up as follows, with a clear and schema load, as this process if for creating a new record.
inspector.Clear();
inspector.LoadSchema(standaloneTable);
Upon modifying the Subtype of the record, adding some attribute values, and attempting to save the new record as follows:
EditOperation editOp = new EditOperation();
editOp.Name = "Road Name Create";
editOp.Create(inspector.MapMember, inspector);
I received an error back that the EditOperation failed due to failing on an Attribute Constraint for another Subtype. It seems after load the Inspector hangs on to the default Subtype, even if it is changed in the Inspector.
The Inspector looks as follows when initially loaded using LoadSchema():
Then it is modified to change the Subtype, and add attributes:
In the debugger, the Attribute for the Subtype shows the Subtype code for Available:
And here is the Subtype definitions:
Hi Charlie,
Yes it looks like a bug. I can duplicate your problem. I also see the same incorrect behaviour with EditOperation.ChangeSubType. We'll endeavour to get this fixed for the new release (Pro 2.3)
Thanks for pointing this out.
Narelle
Hi Narelle,
Thanks for the update!
-Charlie
To clarify. This is a bug with changing the subtype when creating a record in standalone tables. Changing the subtype when creating features works correctly.
Narelle