Kevin, I would split the data into hierarchically organized files on the U2 end if need be. In my experience anything past the multi-value level becomes awkward in any Pick system if you want to use the data for reporting. Sub values are still reasonably well handled with Basic but after that it gets more and more messy. And even if you can nest data far deeper than 4 dimensions using XML or JSON, do you really want to do it, though? Just because you can doesn't always mean you should.
just my 2 pennies Mecki On 12/12/2010 03:42, Kevin King wrote: > In our JSON implementation (moving information between U2 and PHP) we've > artificially limited the data coming into U2 so that it doesn't go deeper > than (effectively) multivalues. We allow the data going out of U2, however, > to be nested significantly deeper. For this product the limit isn't a > problem but I would love to find a sensible way to parse a JSON string of > any depth or complexity into a U2 structure that can be easily consumed by a > program. > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users > _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
