Filemaker has no built in way of copying objects between databases and so much be done manually.
The order in which you copy things is very important.
ie, if you copy scripts before layouts, any script that refers to a layout will be broken
The following should be set before hosting a filemaker database on a server, as once it's uploaded, these can't be changed
Set the view order:
Preset or clear any default global fields
File > Manage > Security > Advanced Settings > Privilege Sets
Confirm sharing settings at a minimum [fmapp] should be full access
Layout Edit Mode settigs
Primary Keys
Default of UUID is good for most cases.
UUIDNumber is better if you anticipate a table with millions of records as the index will be smaller.
Everything in json is an object or an array and contains key/value pairs
keys are inclosed in quotes followed by a colon:
{"first":"craig","last":"hammondus"}
{"person":{"first":"craig","last":"hammondus"}}
{
"person": {
"first": "craig",
"last": "hammondus"
}
}
JSON Type constants. Can use either the name or number.
JSONRaw = 0
JSONString = 1
JSONNumber = 2
JSONObject = 3
JSONArray = 4
JASONBoolean = 5
JSONNull = 6
Functions
These are functions, so they need to be assigned to a variable or data field.
keyOrIndexOrPath
.person.name.first
JSONSetElement
JSONSetElement ( json ; keyOrIndexOrPath ; value ; type )
If you leave json
blank, JSONSetElement will imply a blank json object, so the two following commands will procduce the same result
JSONSetElement ( "" ; "testes" ; "hairy" ; JSONString )
JSONSetElement ( "{}" ; "testes" ; "hairy" ; JSONString )
JSONGetElement
JSONGetElement ( json ; keyOrIndexorPath )