[FX.php List] Re-That sinking feeling: FileMaker 12 & FX ?

[Chris Hansen]

FWIW, FMS has had this bug before.  Perhaps when working on FMS12 they started with a code branch that had the problem...  From my experience, there is at least one big, XML-related bug in every major FMS release.  So yes, if you haven't reported it as a bug, please do so.

It may be a good idea to add code to FX that will handle FM's other XML web grammar (though it's MUCH more verbose, and thus a bit slower), but at least that would give us another option when bugs were found...

Best,

--Chris

On May 8, 2012, at 8:34 AM, BEVERLY VOTH wrote:

> Have you tried the grammar that is used by the FM API for PHP? fmresultset, rather than FMPXMLRESULT? You can't export with fmresultset, but you can make an XML web publishing request.
> 
> The big change in XML (and PHP) web publishing (FMS12) is that the entire set of records is no longer returned if the foundset is 0. Though I don't think this has anything to do with your problem.
> 
> There should *always* be the same number of COL element as FIELD elements and it sound like you are not getting that! :(
> 
> Can you send me your XML results back channel, Troy? beverlyvoth at gmail.com
> 
> It may indeed be a bug.
> 
> Bev
> 
> 
> 
> On 08 May 2012, at 10:15 AM, Troy Meyers wrote:
> 
>> Bev,
>> 
>> Thank you, good test. If I do the XML export for the same layout, same record, the portals that don't happen to have any related records in them produce:
>> <COL></COL><COL></COL><COL></COL><COL></COL><COL></COL><COL></COL><COL></COL><COL></COL>
>> ...indicating 8 empty fields, which is right for the portal.
>> 
>> This is NOT present in the XML Result from the WPE.
>> 
>> The other grammar produces things like:
>> <Disable_Offspring_Photo></Disable_Offspring_Photo>
>> for the fields in the empty portals.
>> 
>> Since the FMPXMLRESULT export is different (other than just the field order) than the WPE's Result output, I'm even more inclined to think that is is a FMS 12 WPE _bug_.
>> 
>> Remember, the WPE output does produce field name items for the empty portal fields in the <METADATA> section, but does NOT produce corresponding <COL><COL/> items in the <RESULTSET> section, so the names and data values end up being misaligned as soon as missing portal data is (not) encountered.
>> 
>> Which is why the FX results are misaligned too.
>> 
>> -Troy
>> 
>> P.S. This is all from a set of PHP pages that have been relatively unchanged for a couple of years, and I've never seen the problem before. Saw it the next day after switching from FMS 11 to FMS 12. In other words, it used to work, now it doesn't.
>> 
>> 
>>> What happens to the XML if you just EXPORT from the same layout? You
>>> should get the same set of elements. Yes, a portal can be empty, but it
>>> sounds like you are getting empty when there are portal rows with DATA.
>>> 
>>> Also try an XML query via web publishing using one of the other
>>> grammers.
>> 
>> _______________________________________________
>> FX.php_List mailing list
>> FX.php_List at mail.iviking.org
>> http://www.iviking.org/mailman/listinfo/fx.php_list
> 
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
>