[FX.php List] Related field issue

[Kevin Futter]

Chris, I can confirm that this is set correctly. I had an issue like this
once before, where an entire file suddenly stopped serving data from
certain fields via XML. I ended up having to rebuild the file from scratch
based on an empty clone.

In this case I've got around the problem by creating a lookup field in
File A that pulls the data locally from File B. This works, but I still
can't figure out why it was necessary. I suspect it's some sort of minor
field-level corruption in File B.

Now that FM has released a patch to FMS(A) that fixes the XML bug (tested
and confirmed -yay!), we'll be moving to FMSA12 in September, so I'll see
what happens after the conversion process.

Kev

--
Kevin Futter
Webmaster, St. Bernard's College
http://www.sbc.vic.edu.au/




On 23/08/12 4:56 AM, "Chris Hansen" <chris at iViking.org> wrote:

>Kev,
>
>Okay, silly question perhaps, but does the FX web user have the correct
>extended web permissions in File B (xml access, in other words)?
>Permissions are definitely a hairy beast, and it's easy to miss small
>stuff.  Best,
>
>--Chris
>
>On Aug 21, 2012, at 10:48 PM, Kevin Futter wrote:
>
>> Hi folks,
>>
>> I've got a weird problem I'm hoping someone can help me with. I'm
>>pulling data out of a table in File A using FX. Today I decided I needed
>>some data out of a field in related File B, so I put that field on the
>>web layout of File A. I ensured all the permissions were correct at both
>>ends, and even logged into File A as the FX web user (to which I gave
>>'fmapp' privileges), and the data is visible on the layout.
>>
>> BUT! When I pull the data out of that layout via FX, I get an empty
>>array element for that field. It doesn't even read the field name for
>>the array index. In desperation, and I added a calculation field to the
>>table in File A that resolves to the data I want from File B. Again, it
>>passes all the tests I did for the pure related field, but still no joy.
>>The only difference is that this time I get the field name in as the
>>array index, but still no data.
>>
>> I have absolutely no idea what's going on! Normally this sort of thing
>>indicates a permissions issue with the related file, but I've opened
>>everything up on both sides of the relationship, and have proved that
>>the web user can 'see' the related data.
>>
>> Any clues?
>>
>> Thanks in advance,
>>
>> Kev
>>
>> --
>> Kevin Futter
>> Webmaster, St. Bernard's College
>> http://www.sbc.vic.edu.au/
>> This e-mail and any attachments may be confidential. You must not
>>disclose or use the information in this e-mail if you are not the
>>intended recipient. If you have received this e-mail in error, please
>>notify us immediately and delete the e-mail and all copies. The College
>>does not guarantee that this e-mail is virus or error free. The attached
>>files are provided and may only be used on the basis that the user
>>assumes all responsibility for any loss, damage or consequence resulting
>>directly or indirectly from the use of the attached files, whether
>>caused by the negligence of the sender or not. The content and opinions
>>in this e-mail are not necessarily those of the College.
>> _______________________________________________
>> 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

This e-mail and any attachments may be confidential. You must not disclose or use the information in this e-mail if you are not the intended recipient. If you have received this e-mail in error, please notify us immediately and delete the e-mail and all copies. The College does not guarantee that this e-mail is virus or error free. The attached files are provided and may only be used on the basis that the user assumes all responsibility for any loss, damage or consequence resulting directly or indirectly from the use of the attached files, whether caused by the negligence of the sender or not. The content and opinions in this e-mail are not necessarily those of the College.