- 2 Views
If you are using Claris FileMaker Pro, you may see this expression in layouts, scripts, calculations from time to time.
"Missing" error warnings indeed indicate that the table, field, layout, script (etc.) could not be found.
This may have occurred for the following reasons;
- Deleting the relevant element
- Elements not defined during
- Copy/Paste External file not found
- User authorization settings
- FileMaker Error (Related article for details: “Table Missing” error and solution)
Let's list the full list of Missing alerts, especially for you to reach this article easily;
- <Table Missing>
- <Field Missing>
- <Relationship Missing>
- <Script Missing>
- <Layout Missing>
- <Value List Missing>
- <Menu Set Missing>
- <Function Missing>
- <File Reference Missing>
Let's detail the cases of getting this error item by item;
- Deleting the relevant element
BUT, if you try to delete a used element, for example a field, you will start getting "missing" warnings in the settlements, scripts and calculations where that element is used. When you try to delete a field, Claris FileMaker automatically checks whether the field is used in scripts and relationships. Similarly, when deleting a table, it checks if it is used in scripts. If used "is it your final decision?" he warns once again.
For other elements, it is completely under your control, you need to know or check whether the relevant element is used or not.
The general rule of thumb is to think 3-4 times, not 2, before deleting any element. In Cabitas, according to our Claris FileMaker development standards, there are fields, table layouts, etc. that should be deleted. We mark elements by adding the prefix "x_" to the beginning of the period name. If this element does not have a serious burden on the database, it waits for a while with its new name for the second evaluation. In this way, we can avoid using this element during additional development, and we will see the places where it is used more practically.
DDR (Database design report) is our best friend to see where any element is used. If you haven't watched it, you can reach the Database Design Report section of our mini FileMaker tutorials here (https://www.youtube.com/watch?v=K8hfVg0xVz8). If developing software in FileMaker is your professional job, another training video is about applications where you can analyze DDRs more easily, the link is here: https://www.youtube.com/watch?v=ZMuPvlfeLkw If “Field Missing” or “… Missing” is really caused by an element that you, as a FileMaker programmer, deleted, the most practical way may be to transfer the updated data to an up-to-date backup file. The easy way to transfer all data between FileMaker files can be done with the Data Migration Tool (training video here; https://www.youtube.com/watch?v=18BpT_0GDsk), which we took as the topic in our mini FileMaker trainings.
If you do not have an up-to-date backup, it is necessary to detect the missing partitions one by one and correct the errors. Elements not defined during.
- Elements not defined during Copy & Paste
Copy & Paste has saved us a lot of trouble. If you are copy-pasting between different FileMaker Pro files, there is an important issue! "Whether the elements in the source we copied are defined in the target"
If an element (field/field, table/table, script/script, special function/custom function) in your source file does not exist in the target file, you can see expressions such as <Table Missing>, <Field Missing> or <Unkown> in the relevant script steps.
A good tip, you can make copying between files more practical with the Clip tool. For detailed information and mini-training on this, you can refer to the following topic https://cabitas.com/blog/filemaker-pano-yonetim-araci-klips?v=1637395969.
External file not found While using Claris FileMaker Pro, you can establish a relationship between tables, you can also add tables from different files to your project, and if necessary, you can establish a relationship with the tables in the other file. The basis of the approach used as the "Data Separation Model" is the relationship between files.