If I have view B which implements view A, in the definition of view B do I need to list the properties (e.g. container mappings) that are “inherited” from A? I noticed that if I don’t list them, this works fine the first time when view B is created (I can see the inherited properties automatically included), but if I try to update view B (even if nothing changes) the call fails saying that there is a change in the property list and the version needs to be changed. I’m assuming this is because the inherited properties are missing from the definition. Is this behavior by design and I have to explicitly list the properties, or would it be considered a defect?
Best answer by Dilini FernandoView original
This one is interesting! I’ll do some digging and get back to you on it.
Apologies for the delay in getting back. I cannot reproduce the behavior you have mentioned above. It was most likely a bug at the time and we have fixed many of them over the last couple of months. Can you please verify again and get back to us if you still see the issue?
Since we haven't heard from you, I'm closing this thread. Please feel free to start a new one if you continue to have issues.