3 Replies Latest reply on Sep 26, 2012 10:50 AM by smcfeeters

    Container data not stored in correct external path

    smcfeeters

      Summary

      Container data not stored in correct external path

      Product

      FileMaker Server

      Version

      12.02

      Operating system version

      OS X 10.8.2

      Description of the issue

      When a PDF is added to a container field, the original document is not stored in the defined external storage location, it is referenced directly from the location it loaded. 

      When the document is dragged to the container field, it is stored in the correct location.  When the document is added to the container field via Applescript, it is not copied to the external data location, hence it is not found by other clients.

      Steps to reproduce the problem

      Create a database with a table containing a container field.
      Create an applescript (based on folder actions) to copy new documents as they arrive in a folder into the database.
      Add documents to the database, first dragging a PDF to the container field, then via the applescript.
      Using Data Viewer example the container field.  Those documents added via Applescript are not stored in the container external storage location.

      Expected result

      Container data to be visible across the network.

      Actual result

      Container data only visible on client that imports it.

      Configuration information

      Client is OS X 10.8.2, running Filemaker Advanced Pro 12.02
      Server is OS X 10.8.1, running Filemaker Server 12.02
      Container storage area is relative the Server database directory

      container.png

        • 1. Re: Container data not stored in correct external path
          philmodjunk

               It may be helpful to post the portion of the apple script used to insert the file.

          • 2. Re: Container data not stored in correct external path
            smcfeeters

                 The applescript used to populate the container is:

                  

                  

                 on process_item(this_item, new_name, results_folder)
                 -- NOTE that the variable this_item is a file reference in alias format 
                 -- FILE PROCESSING STATEMENTS GOES HERE 
                 try
                 -- the target path is the destination folder and the new file name
                 set the target_path to ((results_folder as string) & new_name) as string
                 if running of application "FileMaker Pro Advanced" is false then
                   tell application "FileMaker Pro Advanced"
                      activate
                   end tell
                   delay 1
                 end if
                 with timeout of 900 seconds
                   tell application "FileMaker Pro Advanced"
                   activate
                   getURL "fmp://192.168.2.6/FaxData.fmp12"
                   delay 4
                   go to layout "FaxData"
                   create new record
                   go to the last record
                   set field "Data" of current record of front window to (this_item)
                 end tell
                 end timeout
                 on error error_message
                 tell application "Finder"
                 activate
                 display dialog error_message buttons {"Cancel"} default button 1 giving up after 120
                 end tell
                 end try
                 end process_item
            • 3. Re: Container data not stored in correct external path
              smcfeeters

                   I found a workaround.

                   The Applescript that was putting the PDF in the container field, now just puts the path to the PDF in a field on the record in question, and then invokes a Filemaker script.  The filemaker script puts the path into a variable and using Insert PDF moves the file into the container.  This causes the PDF to stored remotely vs locally.