#BASEELEMENTS SFTP HOW TO#
#BASEELEMENTS SFTP PATCH#
#BASEELEMENTS SFTP UPGRADE#

#BASEELEMENTS SFTP HOW TO#

Not only does it fit the same amount of info in less space, it’s much clearer where you are, and how to get back up the chain of hierarchy. I’ve long thought it to be a bit disjointed, and not as clean as I would like, and so I spent a lot of time iterating on the layout and coming up with a better design. Improved interface designįirst the biggest change is to the main toolbar at the top. There’s some cool changes, and some differences between 18 and 19. Yes, it’s out in beta, you can get a copy here : I’m also considering a monthly option for those who would prefer it, and will have more to say about licencing in the future. I think the addition of the annual licence model in BaseElements is going to be key here, as we keep active and up to date on a more regular basis. This is exciting for BaseElements as it also means we’ll be tracking new functionality in real time. Faster Iteration and releasesįileMaker has also talked about a new faster cycle of releases, moving from annual to more like quarterly with new features coming more often.

I’m looking forward to having a play with this for future releases.

#BASEELEMENTS SFTP PATCH#

At this stage it’s not clear if FileMaker will in some future release automatically “diff” two versions of a FileMaker file, and produce a patch, or if it’s something that developers, and tools like BaseElements will have to generate.īut I see BaseElements as fitting into that niche either way, as the data inside BE is in its own structure, but can be output in any format you like, so BE can generate patch files based on two versions of a solution. It uses the Save As XML formats to document the changes, and can be automated in a closed FileMaker file.Īlthough the tool itself is documented well, the process to build a “patch” file is only described. This is going to be the start of a huge shift in how we do changes to solutions in FileMaker.

#BASEELEMENTS SFTP UPGRADE#

However alongside FileMaker 19, we also got the release of the “ Claris FileMaker Custom App Upgrade Tool” which is complementary to the data migration tool we’ve previously seen. FileMaker now has a “Save As XML” option which is great for for documenting a solution, but still not quite a DDR replacement. I think the other interesting aspect of FileMaker 19 is how the platform is talking about developer tools and how we integrate directly with our solutions out in the field.

A insightful take on this is from Todd Geist, describing FileMaker 19 as the “ first open platform“. This release is a big one in terms of the changes and direction in the platform, and the deeper integration of JavaScript and the Data API into FileMaker Pro client is going to be massive. As always we are hot on the heels of the FileMaker Pro 19 release to announce a new version of BaseElements, v 19.0b1.

Baseelements sftp