2 Replies Latest reply on Feb 19, 2017 3:20 PM by user26751

    Locking a container field during import /update existing records


      How do I lock  specific containers  and protect the files stored inside those containers  during an Import /Update existing records?


      I have a filemaker file  with one table and 100 containers which I sent to my customers. my customers fill the containers and send back the file to me.

      I import the file (import/ Update existing records or matching fields)  and update my version in my dtabase- Then I review every container file and approve (APPROVED checkbox) or reject  (REJECTED checkbox) and add remarks for each file.

      I now export again the file and send it again to my customer whom  corrects and send it back to me.

      To avoid any mistakes I want to lock the containers that have been approved prior to perform another import update existing record. My customer may have deleted or changed by mistake a previously approved file  and I do not wish that specific approved container to change.


      I am using today  for each container  an option "VALIDATE" "ALWAYS"  and VALIDATED BY CALCULATION ( Approved # 1 ). meaning the data in this container can only be cut, pasted or changed if the APPROVED checkbox #1

      Using this method I protect my approved containers from any accidental Delete, Cut or Paste new file.

      It works fine even  during import if only one container is locked. if more than one container is locked or  Say now I empty container 1  and container 2 ,  set them to Unlocked ( APPROVED checkbox = 0) in my database  and  lock container 3 . ( APPROVED checkbox = 1), I Import again the customer file , Nothing will happen. the import  Update new records will exit on Error


      How can  Lock multiple container during  import update existing records?


        • 1. Re: Locking a container field during import /update existing records

          don't import.


          Setup a relationship between your main file and the file you send to clients. The relationship has to have, additionally to other criteria, a condition between a constant in your main file and a variable in the client file.


          When client sends back the file, put it at the same place and do a relookup based upon the relationship. Obviously you'll have to setup your containers accordingly.


          Only the fields (containers) depending both on your criteria and on the rejected condition should update, if you set up everything correctly.

          • 2. Re: Locking a container field during import /update existing records

            Dear Sir

            thanks a lot for your prompt reply

            is there a possibility to do this with Calculation instead of lookups? i am not so familiar  with lookup.

            after I get the file from the client. place it at the location of the related table. how do i trigger the process?