Generalisation-specialisation: error retrieving object-to remove

2
Having 3 entities: two specializations (A,B) under one generalization G. In runtime I want to be able to remove A and create B, maintaining the common attributes of the object in G. Defining a create-action for A followed by a delete object-action for B causes an error: Object with the following id couldn't be retrieved: '[MendixIdentifier:: guid=281569465991243 objectType= (..) objectTypeHash=22 dataStoreCode=1 objectStoreId=75]'. Note: there was no stack-trace available. Is this an aliassing-problem or is the object locked in DB? What should I do/ is there a better way?
asked
1 answers
0

For switching between specialisations I do have an acceptable work-around myself: create a microflow with input-object A and output-object B. Then create a Java-call with object A as input, object B as output. Within Java-call : 

// BEGIN USER CODE 
IMendixObject storeObject = __A; 
Core.remove(this.getContext(), __A); 
Core.commit(this.getContext(), __A); 
return storeObject; 
// END USER CODE

Do not forget to import core-class. Continue with Create object (for B), Change object (for B) followed by close form & show form ("in content").

answered