5 Replies Latest reply on Sep 2, 2010 9:09 PM by BruceHerbach

    Changing the TO for a layout merge field breaks the DDR

    nickorr

      Summary

      Changing the TO for a layout merge field breaks the DDR

      Product

      FileMaker Pro

      Version

      FMPA 11v3

      Operating system version

      Mac OS 10.6.4

      Description of the issue

      When you have a merge field on a layout from the layout's TO and you change it to a related TO, the merge field continues to show valid data in browse mode, but the DDR reports a broken field.

      Steps to reproduce the problem

      Create a new file with two tables and one field in each table, all named differently.  Add a cross product (X) relationship between the two table occurrences.

      On the layout for Table 1, add a text object and a merge field like "<>".  Check in browse mode that the object is showing valid data - you will need to add a record in both tables.

      Go into layout mode and change the base table for the layout to Table2, the other related table, but don't alter the merge field or click into it at all.

      In browse mode, verify that the merge field still shows the related data from Table1 as before.

      Generate the DDR and look at the Field list for that Text Object.

      Expected result

      First, the field shouldn't show any data when the TO is changed.  Because the merge field doesn't specify a TO, it should use the layout's TO and because "Field1" doesn't exist in Table2, the merge field should show a "Field Missing" error.

      If it's going to retain the Table1 field, it should change or indicate in some way that it's using the Table1 TO.

      Secondly the DDR should report accurately what is happening, so if it is still valid and showing data from Table1, then the DDR should report it as such.  If not, then the DDR is accurate (ie it's a field from Table2) but the field shouldn't work fine as is.

      Actual result

      First the field works, even though the field reference <> is no longer valid and doesn't change to reflect that.

      Secondly the DDR reports the field as :



      Which is that it's a field in Table2, but with a bad id and no name.  So even though the field is still showing data from Table1, the DDR thinks it's from Table2 and is mis reporting what is actually happening.

      Exact text of any error message(s) that appear

      NA

      Configuration information

      NA

      Workaround

      If you click into the field and back out it will attempt to change the TO and so will show the literal text "<>" and so not show an error at all.

      You would need to manually specify the TO for any merge field once you had edited the text.