What features exists in FileMaker Pro 2024 that would compel me to upgrade from 19?

[dmontano]

I have looked high and low to see if the new FileMaker Pro 2024 has these features:

1. The ability to organize Value Lists in folders.
2. The ability to organize Custom Functions in folders.

We have folder organization for Layouts and Scripts, why not Value Lists and Custom Functions?

I understand layout calculations are a feature that does not exist in 19: this appears to have its advantages and disadvantages.

Are there any features that I am really missing out on?

Bear in mind, I am using this database for just myself - not "deployed nor on a server". 

 

[comment]

There are only 2 compelling reasons to upgrade:

1. Security
2.  OS compatibility

WRT security, you may want to read the paper posted here:
https://fmforums.com/files/file/136-security-changes-and-enhancements-in-filemaker®-pro-21/
and decide for yourself how critical these issues are for you.

WRT OS compatibility, it's hard to say. Claris publishes only minimal requirements, not backwards compatibility.

Everything else is just "nice to have", unless you have some very specific needs that could not be implemented in earlier. If you already have a working solution, then that's not the case.

 

[Ocean West]

The current in market product does not have folders for value lists or custom functions. The coming release in a few weeks 2025 v22 will not have folders for value lists but will have folder in custom function (however it removes the ability to sort custom functions - it will re appear in a future version) 

Layout calculations are fantastic to reduce schema in tables just to provide calculated data - however we've had this in 19 by using single segment button bars to accomplish similar efforts. 

if you wan't to hear about the upcoming features please sure to join the webinar. Claris Webinar

 

[dmontano]

3 hours ago, comment said:

WRT security

I had to look this up! 

 

3 hours ago, comment said:

Everything else is just "nice to have", unless you have some very specific needs

I really can't think of anything.

 

3 hours ago, comment said:

If you already have a working solution

I have a "want-to-be-someday solution" that is taking me "forever and a day" to try and build. I truly believe this has become my Moby Dick: I have become obsessed with trying to have something that is "ready-for-use". Out of all other endeavors I have tackled in life - FileMaker is the one I am no where close to mastering and it bogles my mind.

 

Appreciate your feedback to my question - thanks!

[dmontano]

1 hour ago, Ocean West said:

The current in market product does not have folders for value lists

This seems like such an obvious need. And, it would seem to align with the Layouts and Scripts folder feature.

 

2 hours ago, Ocean West said:

Layout calculations are fantastic to reduce schema in tables

I see this as a benefit as well, but it also has me scratching my head if Layout Calculation results can be exported like field data, or if it is strictly for display. In other words, perhaps it is not data that can be utilized like field data...?

 

Thank you Stephen for your feedback.

[Ocean West]

Well layout calcs are to help in your interface without burden of fields. If the text object has a name you could probably fetch the value of it with GetLayoutObjectAttribute 

I use layout calcs to clean up interface for example, instead of just having fields ready to view and enter, I have process were users enter an "edit/find" that pops up a card or switches to another panel but at rest the basic customer info is just a block of text with out clutter of fields labels & borders, I think it easier for a user to consume and more compact, as opposed to the traditional method. -

Personally I would advocate to develop on a server you have the benefits of automatic backups while you are working, for $30 a month you can get a single license for FMPro and a cloud hosted server - check it out: https://www.ottomatic.cloud/ottomatic-essentials-filemaker-hosting/  you could even fully test web direct and FileMaker Go. 

Let(
	[

		//fields
		~fn =
		TextFormatRemove( Jobs@People_CUSTOMER::ContactFullNameFirstLast);
		~cn = TextFormatRemove( Jobs@People_CUSTOMER::CompanyName);
		~p1 = TextFormatRemove( Jobs@People_CUSTOMER::Phone_Day);
		~pe1 = TextFormatRemove( Jobs@People_CUSTOMER::Phone_DayExt);
		~pc1 = TextFormatRemove( Jobs@People_CUSTOMER::Phone_DayComments);
		~p2 = TextFormatRemove( Jobs@People_CUSTOMER::Phone_Alt);
		~pe2 = TextFormatRemove( Jobs@People_CUSTOMER::Phone_AltExt);
		~pc2 = TextFormatRemove( Jobs@People_CUSTOMER::Phone_AltComments);
		~pf = TextFormatRemove( Jobs@People_CUSTOMER::Phone_Fax);
		~pm = TextFormatRemove( Jobs@People_CUSTOMER::Phone_Mobile);
		~e1 = TextFormatRemove( Jobs@People_CUSTOMER::Email);
		~e2 = TextFormatRemove( Jobs@People_CUSTOMER::EmailAlt);
		~nn = TextFormatRemove( Jobs@People_CUSTOMER::NickName);

		//format
		_fn = TextColor( TextStyleAdd( ~fn; Bold + Uppercase); RGB( 160; 16; 14));
		_nn = TextSize( "Pronounced "; 9) & ~nn;
		_cn = TextColor( TextStyleAdd( ~cn; Bold + Uppercase); RGB( 160; 16; 14));
		_p1 = TextSize( "Phone "; 9) & Trim(
			~pc1 & " " & TextStyleAdd( ~p1; Bold) & Case(
				not IsEmpty( ~pe1);
				TextSize( " Ext: "; 9) & ~pe1
			)
		);
		_p2 = TextSize( "Alt "; 9) &
		Trim(
			~pc2 & " " & ~p2 & Case( not IsEmpty( ~pe2); TextSize( " Ext: "; 9) & ~pe2)
		);
		_pm = TextSize( "Mobile "; 9) & ~pm;
		_pf = TextSize( "Fax "; 9) & ~pf;
		_e1 = TextSize( "Email "; 9) & ~e1;
		_e2 = TextSize( "Alt Email "; 9) & ~e2;
~role = JOBS@::Cust_Role_Primary ;
~add = List ( 
JOBS@::Shp_Address1 ;
JOBS@::Shp_Address2 ; 
JOBS@::Shp_AddressCity & " " & JOBS@::Shp_AddressState & " " & JOBS@::Shp_AddressZip ;
JOBS@::Shp_AddressCountry

)
	];
	List(
		Case( not IsEmpty( ~fn); _fn);
		Case( not IsEmpty( ~nn); _nn);
		Case( not IsEmpty( ~cn); _cn);
		Case( not IsEmpty( ~p1); _p1);
		Case( not IsEmpty( ~p2); _p2);
		Case( not IsEmpty( ~pm); _pm);
		Case( not IsEmpty( ~pf); _pf);
		Case( not IsEmpty( ~e1); _e1);
		Case( not IsEmpty( ~e2); _e2) ; 		
        Case( not IsEmpty( ~add); ¶ & ~add);
		Case( not IsEmpty( ~role); ¶ & ~role )


	)
)