Claris FileMaker 2023 (v20) - New Features and more

On Tue. April 25th Claris International Inc. released Claris FileMaker 2023 (version 20) of FileMaker Pro. This video covers the release from a developer's perspective.
Link to the files on ISO FileMaker Magazine.
www.filemakerm...
Need more information about Claris FileMaker 2023.
Visit this link to start a free trial or get additional details.
www.filemakerm...

[@jaybogartsupport]

So many years had passed Still can't make a video a Background on Layout. Also, Can't make a search bar capable of handling a quick search on 200,000 records. The program lags on search.

[@filemakermagazine]

Just a note about the Perform Script with Callback. It is asynchronous (independent executions). So the remainder of steps should execute until after the server side script is finished, whereupon the Callback script is then executed after the server side script completes.

[@TARagsdale]

WHY WHY WHY do I only have "File" "Edit" "Tools" (I turned that one on) and "Help"!!! I've searched everywhere and there is no mention of how to get the other menu options (specifically "Scripts") ... Help!

[@rvdh1964]

Thanks for your video on FM2023. Could you PLEASE make a video on how to send html emails from FM?

[@filemakermagazine]

Ok. I'll add that to the queue.

[@neilnguyen8988]

Hi @FileMakerMagazine, I have a question: What is different between 2 options below: 1. Perform Script on Server [Wait for completion: On ] ----> Perform Script [ Get(ScriptResult) ] 2. Perform Script on Server with Callback [ Callback script-Parameter: Get(ScriptResult) ]

[@PhilipFemano]

Wait, regarding your demo of OnWindowTransaction, I thought the purpose of your "auditLog" field was to serve as a holding field that captures ANY field that was just modified within that table. But your example is hardwired to a single field named "field" and can't track any random field that's modified. In that case we can just apply an OnObjectModify script trigger to that specific field named "field". Obviously after you commit the value (ie, click out of the field into another field) the calculation field "auditLog" loses the name and value of the field we want to log (if we define that field's value as Get(ActiveFieldName) and Evaluate(Get(ActiveFieldName))! So how do we capture the value of ANY field that we just previously modified but is no longer the active field?

[@filemakermagazine]

Great question. I was only using a single field to keep things simple for demonstration purposes. The key take away is that YOU get to specify which fields you DO and DON'T want. The "ride along" field specified for the event trigger can be WHATEVER (and HOWEVER MUCH DATA) you want. Meaning you can specify the modification user (although this can be automatically tracked in your log table), the fields desired and anything else you want to track. YOU then get to determine WHERE that data goes. You can send the data to another table in the same file (although you have to configure your OnWindowTransaction script to "ignore" said table) or you can push it to another file (suggested) or to a file on disk or many other possible places. The one thing you'll rarely (probably never) do is log the data into a field on any of the records being modified. Essentially, you can't, because the event would fire infinitely. Thus, the best you'll get within the same file is a dedicated table which can hold a record of field level modifications for each New, Modified or Deleted record within a transaction. Note: A single transaction can affect, and include multiple records! So, you would need to break this data out if you want it associated to its respective tables. With regards to the whole "losing the name" the original value would have been captured previously when the record was created as new. You'll have to play with the new feature because your notion of a field level "audit log" is distracting you from how the feature actually works. Yes, you can use it to create a user facing log of which fields where changed from->to on a per record basis, but what can be done with the event is much more than that.

[@Jameyperagine]

How is the "Filemaker_BaseTables (sql)" used in Filemaker? I saw that you said the parenthesis were a mistake but how do you use that functionality?

[@Jameyperagine]

I see you can use that in an ExecuteSQL call.

[@filemakermagazine]

Yes, there are various techniques where you can use ExecuteSQL in order to get metadata results about your solution. This can then be used to generate data structures which can be used to enhance your solution or add various features.

[@djha1257]

It is better to use Microsoft Access if you are a window user. Also it is better to use Libreoffice Base if you are a Mac user. FileMaker's price policy is crazy.

[@DrJohnPollard]

RIght on brother. Although those programs are both crap if you ask me, which no one does. 😇

[@codegocomau]

There are many differences between MS Access/LO Base and FileMaker. One crucial factor is the ability to reliably host the file to more than 10 users: with FileMaker you can open the file with FileMaker Server and you're done. Yes, that ability costs money - but far less than translating from MS Access to MS SQL Server, moving the tables across and updating all of the queries and views that have been defined in the Access file. Sometimes, it's worth spending money to avoid effort and concern, but each of us will have a different idea of what that entails. I'm not going to recommend a particular solution without knowing more about what the other person's goals or values are.

[@onurbaki543]

Thanks Matt.... I hope WebDirect shooting Blank screen has been also fixed with this version.....

[@filemakermagazine]

I don't personally use Web Direct very much but I know they've been giving it a lot of attention and this version saw a lot of fixes. See if your issue is in their support page about server. help.claris.com/en/server-release-notes/content/index.html

[@luckyguy49]

thanks, Matt

[@filemakermagazine]

Thank you for the continued support!

[@Attila_G]

Unfortunally the (confirmed) Kiosk mode bug that I reported month ago still exists in FM20 🙁

[@filemakermagazine]

They likely can't get to all possible fixes. At least you can report the bug on the community site..

[@hawkdriver0171]

My brain is stuck at v11😬

[@duberneys]

Compatibility with Server 19.x None.

[@filemakermagazine]

Actually, Client 20 will connect to Server 19.4.2+. You can find the Interoperability in the link in this comment. 18, however, does not factor in. Typically, Claris has been supporting one version behind (max 2 that I know of) with server releases. support.claris.com/s/article/Claris-FileMaker-2023-Technical-Specifications?language=en_US

[@duberneys]

@@filemakermagazine Thanks. I use Filemaker since Claris 2.1

[@artofplatinum]

What an annoyingly long way to present so little information.