Leaderboard

Actually, there is a way to measure it - but it takes quite a lot of work... MeasureBeforeDisplay.fmp12

@LaRetta shared this sample file with me @comment and I really liked the concept so I played around with it a little. I was able to accomplish the same result with a single layout, which means I'd be more likely to use this technique myself. I also added layout objects so I could measure the various part sizes rather than having to keep a layout size and script config in sync; this is optional and only my preference for maintenance reasons, though. @IlliaFM Since you just mentioned a footer, I added that to my sample file as well. If you try to use my alternate implementation of this technique, be aware there are two fields layered on top of each other that probably only look like one field at a glance. This doesn't solve the other issues @comment just mentioned, though. MeasureBeforeDisplayDS.fmp12

Here is another way you could do this. It uses conditional formatting to identify the exact items that cause the conflict with other orders. Again, more work is required if you want to see exactly which overlapping order has the offending item, but it might not be worth the trouble. BookingItemsConflict.fmp12

Is it safe to assume the context is an Order with a portal to LineItems? If so, I would do something like the attached. Re your calculation, I don't understand the logic it attempts to implement. And I don't think it can be done by calculation alone. Depending on the format you need this, there may be a much simpler alternative: sort your line items by ProductID and use a summary field that counts them with restart. This will work if you print your orders from the LineItems (as you should), as well as in a sorted portal. SimilarChildrenNumerator.fmp12

Such manipulation is certainly possible, using either the While() function or a recursive custom function or even a looping script. However, it is far from being a convenient way to process data. Filemaker is designed to store data in a structure of records and fields - and it has plenty of built-in tools to assist in processing such data. In the given example, sorting the data by date and by employee, and summarizing the amounts (?) using a summary field would allow you to produce the expected result much more easily. If your data is actually structured properly as a table of Employees and a child table for the amounts (where each amount is a separate record with fields for Date, EmployeeID and Amount) then I would suggest you start there instead of producing the "Input List" first then try to wrestle with it.

"What a coincidence, so do I!"

Not really. Because we still don't know what the result should be when the decimal is below .1 or above .4. I am guessing (!) you want to do something like: Let ( [ r = Mod ( final ; 1 ) ] ; Int ( final ) + If ( 0 < r and r < 0.5 ; 0.5 ; r ) ) which would give the following results in my example: 1.0 ==> 1.0 1.1 ==> 1.5 1.2 ==> 1.5 1.3 ==> 1.5 1.4 ==> 1.5 1.5 ==> 1.5 1.6 ==> 1.6 1.7 ==> 1.7 1.8 ==> 1.8 1.9 ==> 1.9 2.0 ==> 2.0

No need to apologize, I just wanted to make it extra clear in case someone else is reading this. The term "scan" is actually used in the help for this function: https://help.claris.com/en/pro-help/content/position.html Note that the same principle applies to the start parameter too. Both: Position ( "123456789" ; "7" ; 1 ; 1 ) and: Position ( "123456789" ; "7" ; 5 ; 1 ) return 7. Because you always count from the beginning of the text, regardless of where you started and in which direction you searched.

You can construct the calculation along the lines of: List ( "image:Photos/" & ArtistName & ".jpg" ; "image:Photos/" & ArtistName & ".png" ) This will create both paths as a return-separated list. The container field will then go over this list and display the first image it can find.

Here are just 2 ideas that spring to mind: Let ( [ lastChar = Right ( Trim ( text ) ; 1 ) ; lastPos = Position ( text ; lastChar ; Length ( text ) ; -1 ) ] ; Left ( text ; lastPos ) ) or: Let ( tmp = Trim ( "a" & text ) ; Replace ( tmp ; 1 ; 1 ; "" ) )

I see no difficulty in going to the related table and creating the records there. Sometimes it is easier to use a relationship, but the difference is minute, not "infinite". If there is a need to show a portal based on the same relationship, I would much rather add a few steps to the script than muck around hiding the objects in the portal.

The space character is the character immediately after the last hyphen in the text. Suppose the text were just: "a - b". The length of this text is is 5, and the position of the hyphen is 3. 5 - 3 = 2, so your expression: Right ( db ; len - lastSpace ) will return the last two characters of the text, i.e. " b". It depends. If the hyphen separator is always followed by a space, you might simply subtract it: Right ( db ; len - lastSpace - 1 ) A better solution would look for the position of the entire separator pattern " - " (a hyphen surrounded by spaces) and do: Let ( [ len = Length ( db ) ; lastSeparator = Position ( db ; " - " ; len ; -1 ) ] ; Right ( db ; len - lastSeparator - 2 ) ) This would allow you to correctly extract "Carter-Brown" from "Smith - Jones - Carter-Brown". If you cannot be sure the space/s will always be there, you may use Trim() on the result (this is assuming the extracted portion will not contain any significant whitespace characters).

Hello all, We're currently testing with FM Starting Point 24.0x5 USS and having trouble locating the best place to modify the default window size setting(s). Which script(s) should we be modifying to increase the default window size?

I am afraid we are not talking about the same thing. My suggestion is to divide the problem into two parts. In the first part you define a self-join relationship of the Orders table that identifies orders that overlap the current order's time span. This is easy to do using the existing, stored, fields of the Orders table: Orders::DateIn ≤ Orders 2::DateOut and Orders::DateOut ≥ Orders 2::DateIn and Orders::OrderID ≠ Orders 2::OrderID The second part is to identify which of the overlapping orders are conflicting - i.e. have a same product. This could be done in a number of ways, for example filtering the portal to Orders 2 by a calculation of: not IsEmpty ( FilterValues ( Orders::ProductIDs ; Orders 2::ProductIDs ) ) where ProductIDs is an unstored calculation field = List ( LineItems::ProductID ) Any records displayed in such filtered portal would be conflicting. You will have to make an additional effort to see exactly why they're conflicting, but perhaps it does not matter? Anyway, the idea is that the number of overlapping orders should be fairly small, so using an unstored calculation to find the conflicting ones among them should be sufficiently quick. Otherwise I see no choice but to move to a denormalized solution where the dates need to be replicated in the LineItems table, and you must take great care that this happens on every relevant layout, in every relevant scenario. --- Caveat: untested code.

I don't know (I am currently stuck at v.18). But I wouldn't be surprised if it's still the same.

I am not sure what exactly you are asking or what to look at in the attached file. From what I can see, the JSON in the GRANT::JSON field in the 4th record of your file is properly formatted - at least by the rules that Filemaker uses for formatting JSON (there is no official standard for this and you may see various online formatters return different results). Well, Grant in your JSON is also an array. The keys of any array are the numerical indexes of the array's child elements. The District array is a grandchild of Grant, and you will see it listed if you look at JSONListKeys ( GRANT::JSON ; "Grant[0]" ) or JSONListKeys ( GRANT::JSON ; "Grant[1]" ) and so on.

@fbugeja I notice you have cross-posted this question on Claris Community. This doesn't happen very often, but the answer you received there is better than any of the other options mentioned here. It may not be easy to understand at first glance, but I think it's worth spending the necessary time to learn it.

Filemaker has a simple and reliable mechanism to number all records in a table (regardless of type) sequentially: https://help.claris.com/en/pro-help/content/automatic-data-entry.html Your proposed numbering scheme, which would require maintaining a separate series for each type, is not simple to implement - esp. in a multi-user scenario where you run the danger of two users creating a new record at the same time and ending up getting the same serial number. This may not be a task you want to undertake if you are "brand new to FMP". I would advise you to just number all your records sequentially. I doubt anyone will notice the difference. Note also that you don't need a series of custom dialogs to get user input for a new record. They could just fill out the fields directly on a layout and commit the record when ready. Even with a custom dialog, the user can populate up to 3 fields/variables in a single step. And don't use global variables (prefixed with $$) where script variables (prefixed with $) will do.

I presume you are talking about the macOS Character Viewer? You can open it from the Input menu . Re your 2nd question, consider using custom menus or macOS Shortcuts. Please update your profile with your version and OS.

Replace the carriage returns with spaces: Substitute ( List ( Related::Field ) ; ¶ ; " " )

Except for account name: https://help.claris.com/en/pro-help/content/running-scripts-on-server.html

And if you receive the data exactly as you've indicated, I would first convert it into tables and records as Comment suggests. Converting the import can be handled in a single looping script. Once normalized, you can generate reports, place portals on an Employee's layout, and anything else you can imagine. 😀

Sorry, I am not going to look at a script that has 46 or more steps... Yes. If there is no related record in the child table, then setting a field of the child table from the context of the parent will create a new record in the child table and populate the match field of the child to match that of the parent. There are some additional (undocumented) characteristics of this behavior that people have utilized; do a search for "filemaker magic key" for more reading on this.

Not really, because I don't understand why it cannot be the same for everyone. You are not showing us the stored find criteria. If you are searching for the account name, then I would expect to see something like: Enter Find Mode [] Set Field [ SomeTable::SomeField ; Get (AccountName) ] Perform Find [] or: Set Variable [ $accountName ; Get (AccountName) ] Perform Find [ Restore with the variable being used as the stored criteria. I also don't understand why you need different layouts for different users. Surely you don't intend to have 3,500 layouts?? If you have different categories of users that require different layouts, then store the user's category in a field of their record, then go to the appropriate layout after performing the find, based on that field. Or maybe the users belong to different privilege sets, in which case you could branch based on Get(AccountPrivilegeSetName).

The question makes very little sense, because the two functions have very little, if anything, in common. The Case() function evaluates one or more test expressions and returns the result for the first test expression that evaluated as true. The List() function simply constructs a return-separated list of all its arguments. The important point here is that the List() function ignores empty values. So the difference between your: If ( a ; b ) & ¶ & If ( c ; d ) and mine: List ( If ( a ; b ) ; If ( c ; d ) ) is that when a is false and c is true, you will end up with an empty line above d, while my result will be just d. Or, in more general terms, your result will always contain a carriage return, while mine will have it only when both tests are true. And, as Søren already pointed out, the Case() function would only ever output either b or d, never both.

Could also be written this way: Let( tt = final ; Choose( Min( Mod( tt; 1 ) * 10; 5 ); tt & ",0"; Int(tt) + 0,5;Int(tt) + 0,5;Int(tt) + 0,5;Int(tt) + 0,5; tt ) ) (if being outside europe substitute commas with punctuations...) --sd

Make a custom function to tailor each fraction into a desired result: Pease note that I use commas where you probably would use punctuations, for showing where the decimal part starts... --sd

The template is approximately 8 years old, and meanwhile have filemaker undergone some changes in behaviour, the current table also can be portalized! This means we now can utilize native scripted sorting instead. The changes in the sorting comes in later, when I find the time for it🤔 --------------------------------------------------------------------------------- I have now made a template of an idea for the lack of consequence in the sorting in the template form "Hacks" and which to enter something along the lines of the second template attached to this posting. —sd FM SQLPortal Filter & DynSort-3 Copy.fmp12.zip TestofUX.fmp12

No, the sign of the occurrence parameter only tells the engine in which direction from the start position to search. Once a match is found, the function returns its position in the given text - regardless of how it was found. If you want the position from right, you need to calculate it yourself using Position and Length. The exact formula would depend on how exactly you want to count, but perhaps: Length ( text ) - Position ( text ; searchString ; start ; occurrence ) - Length ( searchString ) + 2

First of all, never ask "how to do X using Y". If you don't know how to do X, then ask how to do X, without telling us what to use. Next, your question is not clear because it lacks any context. However, based on your other question (which is also unclear), I am going to guess that this custom function might be what you're looking for: https://www.briandunning.com/cf/908

All I can say at this point is that the problem cannot be reproduced using your description. And I am not going to entertain wild speculations regarding what might be missing from your description. There's probably a very simple explanation right under your nose (https://en.wikipedia.org/wiki/Occam's_razor). I am also not sure what is the point of this elaborate exercise. If you want to make a copy of your file without any records, you can simply save it as a clone (no records). That's one step instead of your steps 1 to 4. And records can be imported directly from the source file, without exporting first. Note also that when importing records manually, you can see in the left pane of the Specify Import Order dialog how many records are in the source table and you can step through them and examine the data in each field of every record. Filemaker offers an extensive report on the file's structure in the form of Database Design Report: https://help.claris.com/en/pro-help/content/documenting-schemas.html. And there are 3rd party tools designed to help with the analysis of a DDR. But Filemaker does not keep track of usage and cannot tell you which elements are unused.

I just wanted to thank you again, Søren. I followed your video and now, all of my records are showing up without any issues. Cheers!

I've just made you a movie, showing what I'm doing: https://www.dropbox.com/scl/fi/xbu6wrwia5lk0fw7e8bee/Sk-rmoptagelse-2024-05-21-kl.-14.24.42.mov?rlkey=1bl493fmgjn0xc226udykdn8q&st=pizpb1qt&dl=0 --sd

Quickfinds aren't stackable as fm-requests are, but you could then loop you through each found set and gather recordIDs in a global, and then finally GTRR(FS) based on the collection af matching IDs. I have made tabbing out as well as typing <return> in the search field, triaging the search: stackedQuickseach.fmp12

MBS Plugin 14.2 was Released today: Your function wish is included: Text.LeftTrim Trims whitespace on the left side. All ✅ Server Text.RightTrim Trims whitespace on the right side. All ✅ Server

Like this - although I think Michael is right about his calc's sansrepeaters.fmp12

Define a repeating calc field with 9 repeatings, containing this: Let( [ tsf = Extend( TotalSchoolFees ); ef = Extend( EnrolmentFee ); ss = Extend( Scholarship ); rg = Round( Div( tsf - ef - ss; 9 ); -2 ) ]; Case( Get( CalculationRepetitionNumber ) - 1; rg; tsf - 8 * rg - ef - ss ) ) Imports from internal tables allows then to split each repeater out into individual records, in a related table, but today with the fm20 "Layout calculation" would I perhaps use the portal row number instead of Get( CalculationRepetitionNumber ) and then get rid of the Extend( shenanigans. Then would only data in the portalized just have one single boolean field, with a checkmark.... --sd

I'll add it to the plugin for you: Text.RightTrim and Text.LeftTrim functions.

We have nothing to base an answer upon. Are you sure you performed a find on the current layout in the current window during the current session? Perhaps Constrain Found Set would be a better choice for this purpose. https://help.claris.com/en/pro-help/content/constrain-found-set.html

Because Claris did not bother to add an "event listener" to monitor variables like they have with fields: OnPanelSwitch_Modified_Again.fmp12

Without knowing exactly what you did, we can only guess. I don't like guessing. Take apart the attached demo file and see if you can spot what's missing in yours. OnPanelSwitch.fmp12

wow! such a quick response; thank you all for your feedback and for sharing your discussion on this topic. some of this needs time to digest to better get my head around the terms and principles involved and thereby appreciate the nuances involved; the posted 'example' file helps with that effort. the remark by bcoony prompted me to review the 'definition' of my newly added field which I had set as type 'numeric' and then I applied a calculation expression to it that yielded the attendent behaviour that was problemmatic for me on this occassion. I decided to change the field type to 'calculation' and for it to yield a 'numeric' result, this has now resulted in the record(s) updating and displaying their value(s) as I require. It would seem that I had 'my horse and cart' configured contrary to my intended requirement/result. in summary, setting a field as type 'numeric' then applying a calculation parameter to it leads to a behaviour that is different to a field set as type 'calculation' then defining its output as 'numeric'. as my understanding and knowledge of this software deepens I feel I'll be able to take on-broad and better appreciate some its nuances discussed above, for now my issue is resolved. your prompt feedback, comments and support are all gratefully appreciated. regards & best wishes, yoyojoe

I am afraid I don't know. I would try removing some or all of the top 3 options, but that's just blind groping. If you cannot make it work through the native Insert from URL step, try the BaseElements plugin: https://docs.baseelementsplugin.com/article/517-behttppost

Hm, what a strange thing indeed. I have never seen such thing, and I would have to run another test or two to be sure, but this is my preliminary diagnosis: Your values are very long, and some of them are identical to others except for a few words at the end. For example, the values under General and Transmission are identical for the first 767 characters. Filemaker indexes only the first ~100 characters. If you look at the field's index, you will see that there are only 3 entries that start with "(COVID 19" - although there are 8 such values. So what probably happens is that when you select Transmission, the correct value is entered into the field - but when Filemaker looks for the corresponding label, it finds General and attaches a check mark to that. I would suggest you use IDs as the values to enter into the field and use a relationship to get the long descriptions. Or (if possible) make sure that the differences between the descriptions occur within the first 100 characters.

This would be a job for a calculation, not a script. You can use such calculation in a script, for example to do: Set Field [ YourTable::Domain ; «the calculation» ] Now, the calculation itself could be simply: Let ( [ start = Position ( URL ; "/" ; 1 ; 2 ) ; end = Position ( URL ; "/" ; 1 ; 3 ) ] ; Middle ( URL ; start + 1 ; end - start - 1 ) ) or even: GetValue ( Substitute ( URL ; "/" ; ¶ ) ; 3 ) -- P.S. Strictly speaking, the substring between "//" and the next "/" is called the authority, and it includes the domain and optionally the port - see: https://developer.mozilla.org/en-US/docs/Learn/Common_questions/Web_mechanics/What_is_a_URL

Here's a simple method to duplicate the found set: Unsort Records Set Variable [ $n; Value:Get ( FoundCount ) ] Loop Set Variable [ $i; Value:$i + 1 ] Exit Loop If [ $i > $n ] Go to Record/Request/Page [ $i ] [ No dialog ] Duplicate Record/Request // perform changes to the duplicated record End Loop

Hello Everyone, I am trying to construct a pedigree tree/chart out of parents and pedigrees for a number of generations in a plant breeding work. Any ideas how to approach this in filemaker or should it be done in JS? Thanks for any suggestion.

Does the attached test work for you? InsertFromRedirectURL.fmp12

Trim( GetValue ( Substitute ( text ; "/" ; ¶ ) ; 1 ) ) This will give you the first value. Replace the last '1' with a 2 to retrieve the second. Hey Bruce, I agree that it is good to study ALL functions but there are 45 text functions so it certainly doesn't hurt to provide a solution from which to learn, no? :-) BrainOnAStick, you might wish to protect from a field with more than one front slash. For instance, what if an address is 141 1/2 E. Main, for example. Just be aware of the potential problem with it.