Jeff: That code's been in production for a few years, getting back the results of an SAP web service (XML) and converting it for use with C_Object. Here's a heads up from the client, who migrated it from V15 to V17:
"In the v15 component, 4D was interpreting certain nodes as Objects. In v17, 4D was interpreting the same nodes as Collections. A new case in the Case Statement “type = collection” fixed it." HTH. -- Douglas von Roeder 949-336-2902 On Wed, Dec 19, 2018 at 10:08 AM Jeffrey Kain via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Awesome - thank you! > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
