Here we want to illustrate how the lookups in a child file can fail. This can occur when a newly created record has new data placed within it's portal. The parent record is still in the process of being created and can cause the relationships in the child file to be temporarily invalid.
By simply exiting the newly created parent record before entering in the portal data, the lookups in the child file work properly.
In the example, click the first button called New Record (portal lookup fails ). A record will automatically be created for SBC as the vendor. Pick one of the expense descriptions and you will see the Amount and Tax Code fields do NOT auto enter via a lookup.
Next, click the second button called New Record (portal lookup works ). A record will automatically be created for SBC as the vendor. Pick one of the expense descriptions and you will see the Amount and Tax Code fields do perform the auto enter via a lookup.
The only difference is the script step in the New Record ( portal lookup works ) button that exits the record before entering into the portal.
An example file can be downloaded by clicking (here)
© 2010 - Dwayne Wright - dwaynewright.com
The material on this document is offered AS IS. There is NO REPRESENTATION OR WARRANTY, expressed or implied, nor does any other contributor to this document. WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE EXPRESSLY DISCLAIMED. Consequential and incidental damages are expressly excluded. FileMaker Pro is the registered trademark of FileMaker Inc.