BE design and JSDO challenges Cancel

1. Patrik Wikström

   

   68 posts
   Registered:
   15 Oct 2018
   20 Dec 2022

   Link to this post

   Everyone can answer 
   
   We have one main table that can be updated and then a read-only child table with meta-data related to the main table.
   
   We populate this child table in ReceiveData, also when updating the main table data
   
   Now when we call SubmitData on the JSDO it will try to merge the changes also from this read-only table
   
   Is this a flaw in our BE design or in the JSDO?
   
   Why we want to return the child table data also when updating the main table is because the change in the main table could be reflected also in this child table data
   
   MERGE-CHANGES in Progress just ignores the other tables by default, doesn't it?
   
   PS. Just delete the previous 2 posts, don't know where they came from? Got some error messages so maybe that caused those and I had to write everything again?

   Last modified on 20 Dec 2022 15:12 by Patrik Wikström
2. Mike Fechner

   

   319 posts
   Registered:
   14 Sep 2016
   Answered

   20 Dec 2022 in reply to Patrik Wikström

   Link to this post

   I believe we ran into a similar or the same issue recently. The JSDO reacted grumpy 
   
   JSDO: In '_mergeUpdateForSubmit()' function, before-image JSON data is missing prods:clientId
   
   when an update of a parent table also returned a child record. We have analyzed the issue and we thing we'll be able to fix this ourselves. We've logged this as SCLNG-620 and will try to include the fix for the next release of the Angular client in January or the following release in February. 
   
   While our testing will be limited to use cases within our Angular DataSource that wraps the JSDO the fix should be valid for solo usage of the JSDO. 
   
   We're not expecting Progress Software to include our changes in the "official" (dead) JSDO.
3. Patrik Wikström

   

   68 posts
   Registered:
   15 Oct 2018
   21 Dec 2022 in reply to Mike Fechner

   Link to this post

   Thanks for your answer!
   
   We also found the place in the JSDO and might get it working for every use case we have, but still remains to be seen.
4. Patrik Wikström

   

   68 posts
   Registered:
   15 Oct 2018
   21 Dec 2022

   Link to this post

   "We're not expecting Progress Software to include our changes in the "official" (dead) JSDO."
   
   Is this really nothing we can do to get Progress more active? Opensource doesn't work for JSDO, as I see it, too small public.
   
   
5. Mike Fechner

   

   319 posts
   Registered:
   14 Sep 2016
   21 Dec 2022 in reply to Patrik Wikström

   Link to this post

   If you want Progress to fix their product, you should log a tech support case. If nothing happens you can seek escalation through your Progress account manager.