Skip to Content
Cascade download Cascade download is a mechanism in which the referring syncbo downloads the referred syncbo’s to any depth during synchronization from device. Cascade download of a referring syncbo would succeed only if all the referred syncbo’s can be downloaded .otherwise, it fails. Cascade download flag can only be set for relationship between syncbos.  Let’s consider four syncbo’s  in design time.image Let’s create the instances of these syncbo’s. The syncbo’s are Timed two way (T01) type.image  Case 1: mobile device synchronizing syncbo A for the first time and all instances of syncbos are present as follows in Replica database.image After synchronizing Syncbo A,  these instances will be present on the device. Bo c – cTop Bo d – dTop, d010 Bo b – bTop, b010 Bo a – aTop, a010, a020   Case 2: mobile device synchronizing syncbo A for the first time and bTop of Syncbo b is absent.image After synchronizing Syncbo A, these instance will be present on the device. Nothing will get downloaded  Case 3: mobile device synchronizing syncbo A for the first time and cTop of syncbo c is not present image After synchronization of Syncbo A , these instance will be present on the device.  Nothing will get downloaded.   Case 4: mobile device synchronizing syncbo A for the first time and dTop of syncbo d is not present.image After synchronization of syncbo A , these instance will be present on the device. Bo c – cTop Bo b – bTop, b010 Bo a – aTop, a010   Case 5: mobile device synchronizing syncbo A for the first time and b010 of syncbo b is not presentimage After synchronization these instance will be present on the device. Bo c – cTop Bo d – dTop, d010 Bo b – bTop Bo a – aTop, a010, a020   Case 6: mobile device synchronizing syncbo A for the first time and a010 of syncbo a is not present.image After synchronizing Syncbo A,  these instance will be present on the device. Bo c – cTop Bo d – dTop, d010 Bo b – bTop, b010 Bo a – aTop, a020   Case 7: mobile device synchronizing syncbo A for the first time and a020 of syncbo a  is not present.image After synchronization Syncbo A, these instance will be present on the device. Bo c – cTop Bo b – bTop, b010 Bo a – aTop, a010 ************  END  ********************** Note: The filter by reference  with cascade download would be dealt in detail in the later blogs. Till then stay tuned.
To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. David Halitsky
    “If it looks like 2-phase commit and smells like 2-phase commit, it MUST be 2-phase commit.”

    Seriously, thanks for posting a very interesting blog above and beyond the usual.

    Regards
    djh

    (0) 
  2. Hi Everyone,

      As said the blog ‘The MI odyssey – Exploring filter by reference’ is published.

    Regards,
    Raghu

    (0) 
  3. Dear Raghu,

      In Case 6 scenario,i hope aTop,a010 & a020 are node level references.If it is correct,then i think without a010,the a020 would not get downloaded to the mobile devices (B’coz there is no immediate parent node instances).please clarify it.

    Warm Regards,
    Ananth.

    (0) 
    1. Here syncbo A has

      aTop – header entity and related to all item(a010,a020) entities,

      a010 – item entity related to header and independent of a020 item,

      a020 – item entity related to header and independent of a010 item.

      In case 6, even though the a010 entity is not present in the RDB, the a020 (independent of a010 ) gets downloaded because aTop is getting downloaded.

      (0) 

Leave a Reply