This means you've have created a file reference which might be pointing to itself. In other words, the field will show on the layout as "Unrelated Table" and won't show any data. This means you've added a field to a layout where the TO of the field isn't accessible from the TO of the layout. However if you sort using the second field, or show only values from the second field, then both fields need to be indexed for the ValueList to work. In fact in that case the second field could be a global or unstored calculation. If your value list is set to "Sort values using : First Field", then the second field doesn't need to be indexed. However it is possible in some circumstances to have a ValueList using a secondary field that isn't indexed. If this isn't the case, the ValueList won't work, and your list will show no data. This will happen when you first create the Value List.
The Primary Field in a ValueList always needs to be Indexed. This may not be an issue and may be deliberate, as you don't need Layouts for all functions, but some functions do require Layouts, and this may cause issues. You could either remove the Table if it's not required, or add some TO's if you plan to use it somewhere. Without any TOs for this Table, it is effectively not able to be used anywhere. Which means you can't even tell what you'd be deleting when you tried to delete it - which you'd be allowed to do. This means you have setup privileges in such a way that you can delete records that you can't view. In other words, you're trying to modify a field that can't be modified. It means you're doing a Cut, Paste, Clear, Set Field, Insert or Replace on a field that is specified as a Calculation or Summary field. This is a simple one to catch, and a good thing to check for. Enabling the script step will cause the broken steps to be active, and this may cause problems, or have unintended consequences. This warning is to alert you that a script step that has been disabled but has errors in it. However it's often the case that a field match from a text to a number that is done by accident will give unexpected results. For example to match on a non-contiguous list of dates, you'd need to put the list in a text field and match the other side to a date field. This means that a "Join Predicate" - otherwise known as the lines matching one field to another in a relationship - are not using the same field type.
The External Authentication process doesn't allow the user to change passwords, so trying to enforce the "Must change password on next login" will cause issues, or allowing the user to change the password will also cause problems. the default file option creates an Admin account with no password, in larger solutions with multiple accounts this isn't best practice. This means you've setup accounts that have no password. These are issues that are related to the functioning of FileMaker, not the output of the DDR. From there you can identify which ones are obvious fixes and should be looked at straight away, and which ones you can leave, and only address if they come up as an issue later.īelow is the explanation and details for each of the items that are currently warnings in BaseElements. The best way to use the warnings function is to look at this list on the setup, and see which of the errors you want to view and or look at, and turn some on or off depending on your development style.
A warning comes about, not because something is broken, but because it will work exactly as it is setup, but there are obvious reasons why the setup might not be what was intended. Warnings are different from "Errors" in that an error is an obviously broken function in the database. Version 1.0.5 and later of BaseElements added the option of a "Warnings" tab to detect issues that may or may not be problems in your solution or may just be issues that you'd like to be aware of.