We are dealing with an issue with IDO definitions not being able to be utilized by certain areas of the system. We have an IDO where the primary key is an automatically incremented integer using the AUTONUMBER() default on the IDO property definition.
From within the context of a Syteline session, this works as expected, the property is automatically incremented when the record is saved. However, when a new record is inserted via the IDO REST API, the default value from the property definition of AUTONUMBER() is not applied and the record insert is rejected due to the property being NULL when a value is required as part of the key definition.
Is this expected behavior when a part of the IDO definition behaves differently depending on the context of records being inserted from a Syteline context vs the API interface? I would have expected this functionality to work in both places as the definition is in the Application Database layer which the API ought also to be able to interact with?
