The new Data File steps, used in conjunction with the new-to-18 error logging script steps, allow us to create error logs automatically. This is quicker and more efficient than was previously possible. Now we can write a line of code to the exported file specifically using the new Set Data File Position step to add our custom headers. Previously we had to use a custom function and some XML to add custom headers to an export intended for Excel. With the new functionality, we can save those individual preferences once to a preferences file, read that file, then use that data without having to re-create the preferences table and record in each solution.Īnother nifty use is adding custom headers to CSV exports.

If a user has three or four distinct apps that have the same preferences – for example, how a phone number is formatted or how they want their name displayed in the database – we would need to store that data in each app. Below is a list of the new steps.Īt the moment, many of us load and save a user's personal preferences within a record in the FileMaker solution. Note that these new steps are probably the most complex of the new functions in FileMaker 18. Granted, all of the functionality was available before using third-party tools (such as Troi File Plugin and the invaluable Monkey Bread Software MBS plugin), but now we can do this directly – natively – within FileMaker.

All of the new steps allow us to create, read and write to and from, and manage external files. more than doubled the file-based script steps so now developers have 21 script steps instead of 10. There are so many new tools in 18 that allow us developers at The Support Group to enhance our customers' applications - I love exploring what can we can do and this time is no exception. releases new versions of their database tools! And, now that FileMaker Pro 18 Advanced is available, I'm still feelin' that love.

Filemaker pro advanced 18