RE: VersionedConcurrencyControl error when adding a child entity (after deleting one)

BIZ TMS XData
17

Hi Wagner,

Please forgive me for going on and on about this subject, but it’s just not resolved:

  1. First and foremost; in the original demo I sent (see earlier in this ticket), the same construction (ObjectXXX implemented) works flawlessly (with the Invoice / InvoiceItems data model).
  2. I have hooked the ObjectXXX procedures only to the child dataset. It then works OK for the children (editing and inserting), but the parent (TDay) is then not persisted to the database (i.e. Version not incremented).
  3. This entire setup with ObjectXXX procedures came forth from this post. In order to persist entities to the database, I somehow need to implement them. VersionedConcurrencyControl error when adding a child entity (after deleting one) - #5 by wlandgraf

Given the above observations, are you willing to further investigate (compare)? If not, what would be your recommended strategy to edit Parent/1-M Children in a form? My current design (load Parent nd use dataset fields seem the most straightforward and simplest approach. Surely this must be possible with XData?