Leaderboard

When you make statements about what is better than an alternative, please qualify the statement. Why is 'choose' better than IF() or CASE() for you? If two or three different approaches produce the same result, how do you select the one you want to use? Performance? What if it doesn't matter and makes the code less readable?

I could not possibly answer such a wide question in a forum post. I suggest you read the help to understand what each of these does and if you encounter a specific question or problem, ask here. I will give you one hint, though: Perform Find[] is the generic way to find records; both Find Matching Records[] and Perform Quick Find[] are shortcuts for specific situations.

Then perhaps you could simply change the timestamp field in the related table to a global field, auto-entering creation timestamp. Then the field will update for all records anytime you create or import a new record. It should be stressed again that this will work only for as long as the solution is not hosted.

If you do not script any part of this process, then you will need to update the timestamp field manually too. Because - as you have found out - if the process ends up with no records being imported into the related table, you have nothing that would hold the timestamp of the import attempt. I don't see why you wouldn't script this, at least in part. Then you can use a global field, in any table.

If all related records have the same timestamp, then there is no point of having the timestamp field in that table. Place it in the parent Products table and make the script that updates the related table update this field too. This is assuming you update the related table for each product separately. Otherwise, there is no point in having the same timestamp replicated in all the product records. Place it in a single-record Preferences table instead.

Yes, that conforms to the trend of "why make it simple, when it can be complicated" - which is so popular in the Filemaker community...

1. You don't know what the calculation does, so you are in no position to judge what is the "better option". 2. I would say that the simplest (and therefore best) way to implement a calculation that is meant to return either 0 or 1 is a Boolean statement. IOW, neither: Case ( test ; 1 ; 0 ) nor: Choose ( test ; 0 ; 1 ) but just: test or (if necessary): GetAsBoolean ( test ) 3. This is completely irrelevant to the question.

New feature, you can choose how the system opens a topic. https://fmforums.com/settings/links/

You CAN import the images independently, but you will have to manually re-associate them with their original records. Here is one way to do it: Make a copy of the Excel file; Rename the copy with .zip extension; Unarchive the .zip; Inside the archive, there will be a folder named media inside a folder named xl. Import the images from this folder. Depends on the web site.

Use an API and let the user authenticate so that you don't have to store credentials. See https://www.soliantconsulting.com/blog/microsoft-graph-api-filemaker-one/ Or if you are on AWS, let the AWS instance check out credentials from the AWS key store and push into FM so that you don't have to store credentials at all.

I am still in v.18. According to the help for the Perform JavaScript in Web Viewer[] script step: And here you will find similar constraints for the opposite direction:

I don't understand what your screenshots show. In general, if you place fields from related table on the layout, they will show data from the first related record. Usually you want to disable entry to such fields to prevent accidental modification.

Yes, but I took the liberty and posted based on your input file on my gist in the link as described in my post above. @comment and my example does the same if you only have 1 record, the one I posted will be able to separate records properly without adding metadata for each record. There are benefits to using the command line tool `tidy`, Xmplify.app or similar in Mac OS X while developing, then again when you are done making it work there are no benefits to line breaks in XML or XSLT. Rather on the contrary different systems may interpret different kinds of separators for line break

Another option is to define a calculation field in the Contacts table as = Role & ":" FullName and another calculation field in the parent table as = Substitute ( List ( Contacts::cFullInfo ) ; ¶ ; " / " ) If you prefer, you can insert a tab character in between the values to better control the spacing. Note that in version 18 and higher the same result can be produced by a single calculation field using the While() function (and in previous versions by a recursive custom function). I am not sure that's a good idea. But that's unrelated to this ques

It sounds like you want a horizontal portal? That's not a built-in option, but you can simulate it by creating single-row portals, each one starting at a different row. I think you will find this much easier to manage than a bunch of duplicate fields.

Hi Craig, Sorry, I don't check on this forums over the weekend. For #1. I notice that you have two Save to PDF script steps. You don't need the first one and just need the second. Make sure that you've selected "without dialog." That would take care of the saving part. For #2. In the email setup dialog, at the very bottom notice the Attach File checkbox. Select the box. And then in Specify enter the $path variable. This should take care of it for you. Let me know if you're still having trouble. David.

I did. Just installed two of them in the last few days. See my last post. In both scenarios: - client had downloaded the license cert the day that FM 19 was released but that only works until June 1st. Claris has since updated the license certs so you need to download a new one - the trial cert also doesn't work so it is not as simple as installing the server in trial mode. Perhaps if you download the "a" variant of the installer but I had the. one from when 19 was just released which is not that latest "a" version. fms_19.0.1.103a vs fms_19.0.1.103 If you are stuc

The AWS CLI for S3 has the native ability to do a sync instead of a full copy. That means that I don't waste time or 'disk space' on S3 by copying files that it already has and that have not changed. I then ask S3 to create a new date/time-stamped folder in my bucket and tell it to copy all the files into it. That's blazingly fast and doesn't tax my FMS at all. Plus I can then set a retention policy so that it keeps enough backup sets but archives old ones. I would suggest you do the same in the copy to your NAS: depending on your OS use either rsync or robocopy (both native to their

View File Toggle switches A sample file with 9 toggle switches, 7 of which have the pressed state. Submitter flusheddata Submitted 06/11/2020 Category Samples FM Version 16

With so many amazing new features in the latest FileMaker release, it may have been easy to miss some of the smaller features. In this FileMaker 19 Q&A, we take a moment to look at some miscellaneous new features. Future live streams: https://fmtraining.tv/#LIVE support@rcconsulting.com www.fmtraining.tv www.fmstartingpoint.com www.rcconsulting.com

It does NOT use 12GB per backup. It's a common misconception. The OS will report the full backup set as being 12GB, and it is, because it is a complete set always with each backup. The FMS uses hard-linking under the hood. Meaning that any files that have not changed since the last backup will not occupy new hard disk space. There is a very easy way to test this. Run a backup and check the free disk space. Wait a minute and run a new backup, check the free disk space: you will see it did not go down by 12GB. It went down by the size of whatever file got created or modified inbe

That sometimes happens when the auto-login feature is still turned on but the pw for that account is now different. Check to see if that toggle is still on and toggle it off.

Here’s a thread on pickers. I posted a demo file.

Yes, I'm aware of all those options. But here's the deal: Filemaker runtimes have allowed me to roll out small targeted label and report solutions to meet Customer requirements, easily and quickly. In each case, the data originates in other systems. Often it is in the form of distribution grids that Filemaker could not possibly process (not a record-based data model). We have Python routines to do the heavy lifting of depivoting this data into a normalized record-format. These are all one-off jobs. Nothing lives in an ERP or other database system. It's project work. The only way to retain

Try = not IsEmpty ( FilterValues ( Scope::FieldName ; ValueListItems ( Get (FileName); "ValueListName" ) ) )