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

Troy Meyers tcmeyers at troymeyers.com
Tue May 8 08:15:20 MDT 2012


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.



More information about the FX.php_List mailing list