Popular Content

Showing most liked content since 04/25/2017 in all areas

  1. 3 likes
    Couldn't this be much simpler? AppleScriptSpeak.fmp12
  2. 2 likes

    Version 1.0.0


    This technique was inspired by @Claus Lavendt in a tweet. Now with offset new card style mode you can now create a tool pallet to interact with a document in preview mode


  3. 2 likes
  4. 2 likes
    See: http://www.filemaker.com/help/16/fmp/en/#page/FMP_Help%2Fextended-privileges.html%23wwconnect_header (the last item in the table).
  5. 2 likes
    That doesn't actually help the user find the answer to his question, it answers a different one, and there are reasons for wanting this one answered.
  6. 1 like
    For this to work, you would need to know when you entered it - for example, by having a field auto-enter the record's creation date/timestamp. Then you could have an unstored calculation field showing the current age (approximately, since you don't know the exact birthdate) . Without this, the only way to achieve what you want would be by running a script once a year to increment the stored Age values by 1.
  7. 1 like
    You have a 'parcels' key/node that is not correct. It should immediately start with an array as per their API, you start it as another piece of JSON with another 'parcels' key name
  8. 1 like
    I get exactly where you are at. My first dive into development was taking a system from FMP 4...and reworking the workflow, and adding a ton of features. With the capabilities of the modern versions of FM, there may be some opportunities to consolidate that down into a single UI file that reaches out to the other files and uses there data. Classic separation model use-case. Good luck with whatever you decide to do, and if you need tips or have questions. You know where to find us!! lol
  9. 1 like
    Hi Cable, The FM Forums is not part of FileMaker Inc., and no one here works for FileMaker Inc. Our members are all volunteers donating their time, knowledge and skills to help other members overcome things they run across when developing files. To continue to express your frustration to us about this change isn't going to accomplish anything. You need to take this up with FileMaker Inc. Lee
  10. 1 like
    "-H Authorization: ShippoToken " & $token & " -H Content-Type: application/json -d " & $json I believe above should make a valid string.
  11. 1 like
    If you take that piece of your code and put in the data viewer it will tell you what is wrong. Look at the output and compare it to what is required. Some quick ones: - you don't need the ampersand after the first -H - you don't add spaces between the different sections
  12. 1 like
    To address the loss of the bottom toolbar during development, I have created a small toolbar which I am putting on every layout with a hide condition if [ not "Full Access" ]  As a result of reading this thread, I think I will be adding additional buttons/segments to include "Show/Hide menu bar[toggle]" and to access layout Mode
  13. 1 like
    FileMaker's 'Open' command will work with Excel and text files -- converting them to FileMaker files in the process -- but not PDF. I believe you can fill in PDF forms using Scribe: 360works.com/filemaker-pdf-plugin/
  14. 1 like
    I move it to Managing Scripts I deleted your duplicate post. Please do not double post your questions.
  15. 1 like
    No. Try the Open URL[] script step to open a non-Filemaker file in its native application. I don't know of a way to do that natively from Filemaker. Perhaps with a plugin.
  16. 1 like
    You can email FileMaker... But as there is only little changes between the versions, you could simply go with 12 and be fine.
  17. 1 like
    Come to think of it, you could probably just use Find/Replace to highlight the found text and to move to the next (or previous) occurrence. This could be scripted, as shown in the attached file. Note that we are using a calculation field to prevent accidental modification of the original. FindNexttInPortal.fmp12
  18. 1 like
    I conducted a small test of my own and I can confirm that including an external stylesheet causes a failure. That's hardly surprising given what I said earlier about the XSLT being applied from memory, even with the BE_ApplyXSLT() function. Strange choice on part of the plugin's author. Yeah, well, that seems to be a separate issue that muddies the waters. The function does not return any error codes - not even a 0 in case of success.
  19. 1 like
    I can confirm there is no error message (using BE 3.3.4). However, the process itself works fine for me. Verify your paths as suggested here: https://baseelementsplugin.zendesk.com/hc/en-us/articles/205350417-Notes-about-File-Paths
  20. 1 like
    I'm assuming you are using a system script schedule on FMS? Then the script itself can only be in one location: the FMS scripts folder. If it is not there you wouldn't be able to select it when you set up the schedule. This could be a permissions issue: both on the script file itself (owner and group has to be fmserver / fmsadmin ) and the script will be executed in the context of that fmserver user. That user needs the proper rights to do what you want; which it may not have.
  21. 1 like
    For the new version, going to test it like mad in the next few days.....
  22. 1 like
    It would. Clicking a button to populate a joining date field would work even better, IMHO.
  23. 1 like
    There is no good reason to add the joining month to the actual membership number. You can easily display the joining date (formatted as MMDDDD) alongside the membership number, if it helps. Although I believe a computer would be much better at keeping track of when it's time to renew a membership than a human eyeball.
  24. 1 like
    We have millions of records in multiple tables, being hammered on by 100 users... And processing 3-5k records at a time. Rarely takes longer than a few seconds. So I'm not sure what you mean. I'll agree, FM will let you build it so it's slow, but that doesn't mean it can't be faster. And as Jeremy said, performance increases are only beneficial to a point. There are so many variables that can make a process or script perform poorly, it's short-sighted to always blame FM for that. Sometimes, and probably more often than we would like to admit, it is the developer's fault.
  25. 1 like
    Here's another: https://www.geistinteractive.com/2017/05/09/filemaker-16-biggest-change-since-filemaker-7/
  26. 1 like
    I am guessing you are having a problem with the "ILR-99999999-1617-20160229-144401-01.xml" file. The reason for this is that all the elements in the file are in a namespace. They are put there by the default namespace declaration: xmlns="SFA/ILR/2016-17" carried by the root Message element and inherited by all it descendant elements. This means all your select expressions select nothing. In order to select an element in a namespace, you must declare the same namespace in your stylesheet, assign it a prefix (an arbitrary string), and use that prefix to address the elements in the source XML: <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ilr="SFA/ILR/2016-17"> <xsl:template match="/"> <FMPXMLRESULT xmlns="http://www.filemaker.com/fmpxmlresult"> <METADATA> <FIELD NAME="LearnAimRef" TYPE="TEXT"/> <FIELD NAME="AimType" TYPE="TEXT"/> <FIELD NAME="AimSeqNumber" TYPE="TEXT"/> <FIELD NAME="LearnStartDate" TYPE="TEXT"/> <FIELD NAME="LearnPlanEndDate" TYPE="TEXT"/> <FIELD NAME="FundModel" TYPE="TEXT"/> <FIELD NAME="ProgType" TYPE="TEXT"/> </METADATA> <RESULTSET> <xsl:for-each select="/ilr:Message/ilr:Learner/ilr:LearningDelivery"> <ROW> <COL><DATA><xsl:value-of select="ilr:LearnAimRef"/></DATA></COL> <COL><DATA><xsl:value-of select="ilr:AimType"/></DATA></COL> <COL><DATA><xsl:value-of select="ilr:AimSeqNumber"/></DATA></COL> <COL><DATA><xsl:value-of select="ilr:LearnStartDate"/></DATA></COL> <COL><DATA><xsl:value-of select="ilr:LearnPlanEndDate"/></DATA></COL> <COL><DATA><xsl:value-of select="ilr:FundModel"/></DATA></COL> <COL><DATA><xsl:value-of select="ilr:ProgType"/></DATA></COL> </ROW> </xsl:for-each> </RESULTSET> </FMPXMLRESULT> </xsl:template> </xsl:stylesheet> Note that I have also deleted the: <COL><DATA><xsl:value-of select="ilr:elevation_m"/></DATA></COL> part from your attempt, because I don't see an elevation_m element in your input nor a corresponding field in the field names you have defined.
  27. 1 like
    That's not a meaningful distinction. "Slow compared to other programming environments" doesn't make FileMaker slow in any absolute sense. "Slow compared to user needs for a particular application" is much more meaningful, and once an application is fast enough to exceed user needs, pursuing additional speed may be wasted effort. FileMaker passes this threshold for many applications, including applications working with millions of records. Working with large data sets efficiently with FileMaker may take additional work, which makes it no different from any other programming environment, and achieving the best possible performance from FileMaker often takes less effort than achieving the best possible performance from other tools. At least FileMaker doesn't claim that processing speed is an absolute top priority, then make design decisions contradicting that every step of the way — just look at what the HPC community has to say about Hadoop.
  28. 1 like
    No, at least not going by your description. There is something else you're not telling us, e.g. a script trigger..
  29. 1 like
    This is cute. And completely not the case in reality. I have seen so many "professionals" try to replicate work we have done in FileMaker, and they have been ridiculously unsuccessful. I don't disagree with some of what you mentioned. There are things I would love to see done differently. But that is also the case with every other programming environment I've dabbled in. To be fully honest, they all suck in their own way. Scale? What kind of scale are you referring to? I ask because I see 2 types of people that say this ( note I'm not implying anything about you specifically, just a general observation ). (1) People who built themselves into a corner, and just set up the data model the "wrong way". For them handling a few thousand records is painful. (2) People who want to process 20 million records in a second or two. Constantly. All day. Yeah, FileMaker isn't that tool. Relatively speaking, the number of companies needing to process millions of records a day is kind of small...compared to the companies that only need to handle a few thousand to a few million records a year. So for developers, this is one tool they have in their toolbelt. And they get paid well for the work they do. That's the definition of professional. Many developers I know have more work than they can handle right now. So it's hard to agree with you on that point.
  30. 1 like
    Yes, it's perfectly possible. In fact, there are two ways you could implement this; one is to loop over the found set in Contacts and create a new join record for each, say (roughly): // REMEMBER THE SELECTED EVENT Set Variable [$eventID; Events::EventID ] // RETURN TO THE FOUND SET IN CONTACTS Go to Layout [ Contacts ] Show Custom Dialog [ ... ] If [ Get ( LastMessageChoice ) = 1 ] Go to Record [ First ] // FOR EACH CONTACT ... Loop Set Variable [ $contactID; Contacts::ContactID ] // ... CREATE A NEW JOIN RECORD Go to Layout [ EventContacts) ] New Record/Request Set Field [ EventContacts::EventID; $eventID ] Set Field [ EventContacts::ContactID; $contactID ] // RETURN TO THE FOUND SET IN CONTACTS Go to Layout [ Contacts ] Go to Record [ Next; Exit after last ] End Loop Commit Records[] End If The other option is to import the found set in Contacts into the join table (mapping ContactID to ContactID), then replace the contents of the EventID field of the imported records with the $eventID value.
  31. 1 like
    The file you have posted is merely an opener file for the real file, and therefore useless.
  32. 1 like
    I think it would be best to start by identifying the problem. But if the field is not on the layout, then obviously you need to put it there: http://www.filemaker.com/help/10/fmp/html/create_layout.9.21.html#1028407
  33. 1 like
    Well, we can only guess. I can think of three reasons why you don't see the number: 1. The field is not on the layout (or perhaps not entirely within the Body part of the layout); 2. The field is empty; 3. The field and the layout do not belong to the same TO.
  34. 1 like
    What makes you think that result isn't accurate?
  35. 1 like
    You can use as many wildcards as you wish. They're evaluated in order, so you simply add the criteria in order. Using the wildcard rather than putting the criteria inline tends to save a lot of headaches. E.g.: ExecuteSQL ( "SELECT DISTINCT id_song FROM T26_SET_SETLISTS WHERE id_staff = ? OR id_staff = ?" ; ""; "" ; $Guitarist ; $Drummer ) I don't think this query will give you the results you're looking for, but if you're interested in going further, start here: https://filemakerhacks.com/2012/10/19/the-missing-fm-12-executesql-reference/
  36. 1 like
    No, not as a portal filter but I guess you could use like that. I would personally use the ExecuteSQL() to collect the IDs, set the IDs in a global text field as a multiline and use it to build the relationship.
  37. 1 like
    pseudo-code for an ExecuteSQL() call that would give you this: SELECT DISTINCT(song_name) FROM join WHERE staff = 'STA01' or staff = 'STA02' or ask for the join id primary key and set that in the global text field to trigger the relationship to the songs table (not the join table)
  38. 1 like
    by far the easiest for you would be to use a multiline key on the left side of the relationship with the IDs of the selected staff: So return delimited list in a global text field: STA01 STA02 Relate to the STA field in the join table will give you a relationship (to use in a portal) to show the songs that they know. Now that may still show duplicate songs in there. You can solve that by using a SQL query for instance to ask for the 'DISTINCT' songs that match both staff but that's a little more advanced, let us know if you're up to working on that.
  39. 1 like
    Are the quotation marks the problem? Sent from my iPhone using Tapatalk Pro
  40. 1 like
    We use client side certificates for GSX webservice from Apple. With our plugin you can use CURL functions and provide client side certificate as PEM or PKCS12 file. See example here: https://www.mbsplugins.de/archive/2017-02-21/Using_Apples_Global_Service_Ex
  41. 1 like
    You should look in Filemaker's File > Manage Database… > Fields, under Type. And since you have the Advanced version, you can use the Script Debugger and the Data Viewer to see what the actual value of the variable is at script runtime, and what does the test return. Yes. And a relationship based on matching the numerical code. Note also that you need a lookup only if you want to store a copy of the looked up address. Otherwise you can just display the related address directly on your layout.
  42. 1 like
    Define a calculation field (result is Text) = List ( ProductName ; "All" ) and base your value list on that. You may want to prepend a space to " All", in order to force it to the top of the list.
  43. 1 like
    Hi Andi You can download a Free Trial of FileMaker Pro 15 here http://info2.filemaker.com/FileMaker_trial_request.html It has a time limit, but you should be able to get a feel for how it works. Check out the example files that is included HTH Lee
  44. 1 like
    That's not a Filemaker-related question. I suggest you start a new thread and post what you have so far: the source XML, your current stylesheet, and - no less importantly - the target field mapping.
  45. 1 like
    It's a long thread, and it would be helpful to pinpoint "this" to something more specific. In general, very little has changed since Filemaker first implemented XML import/export in version 6, so I would expect an old XSLT stylesheet to work just as well with the current version of FMP. Of course, this depends on the source XML schema remaining unchanged as well.
  46. 1 like
    OK - I did it myself. Over a couple weekends of spare time, I wrote a few dozen scripts that interface between Filemaker and the Amazon Marketplace Web Service API. Sad to say, this is non-trivial. Amazon's documentation is poor: there are a surprising number of mistakes, misspellings, and obsolete/outdated sections. The one bright spot is the Amazon MWS Scratchpad, which provides a direct sandbox to allow testing different calls. Most of the documentation and online help is aimed at PHP & Java & Python developers; it's not too difficult to map this into Filemaker land. I wrote scripts to gather my orders from Amazon Market Place, and to send confirmations to buyers. Like most API's, there are many gotcha's. Here's a few hints, mainly to save time for others in my position. 1) A simple Filemaker WebViewer is *not* going to work, unless you do screen-scrapes from the Amazon MWS Scratchpad. 2) I used cURL to communicate with Amazon Web Service via POST. The information to be POSTed is the Amazon parameter string (which includes the hashed signature). The Monkeybread Software Filemaker functions (www.mbsplugins.eu) are just the ticket. 3) The outgoing information must be signed with a SHA256 hash. Again, this is available in the Monkeybread software functions. Use MBS("Hash.SHA256HMAC"; g_AWS_Secret_Key; g_AWS_Text_to_Sign_With_NewLines_Replaced; 1) 4) Getting the correct SHA256 signature requires very strict observance of line-feeds ... carriage return / linefeeds in OS X and Filemaker will cause a bad signature. Before making the SHA256 hash, do a complete replace so as to generate only Unix-style line-feeds. Within the "canonical parameter list" there aren't any linefeeds (but there are linefeeds before that list) 5) The Amazon API demands ISO-8601 timestamps, based on UTC. Filemaker timestamps are not ISO-8601, but there are several custom functions to generate these. The Filemaker function, get(CurrentTimeUTCMilliseconds), is very useful, but its result must be converted into ISO-8601. Notice that Amazon UTC Timestamps have a trailing "Z" ... when I did not include this, the signatures failed. 6) The Amazon API must have url encoded strings (UTF-8). So the output from the SHA256 hash must be converted to URL encoding -- again, the Monkeybread software comes through (use MBS function Text.EncodeToURL) 7) The Amazon "canonical parameter list" must be in alphabetical order, and must include all of the items listed in the documentation. 8) Errors from Amazon throttling show up in the stock XML return, but check for other errors returned by the cURL debug response. At minimum, search through both responses by doing a filemaker PatternCount (g_returned_data; "ERROR") 9) When you're notified of a new Amazon order, you must make two (or more) cURL calls to Amazon MWS: 1) first, do cURL request to "list orders", which will return all the Amazon Order Numbers (and some other info) for each order since a given date/time. 2) Then, knowing an order number, you do another cURL to get all the details for a given order. Repeat this step for every new Amazon order number. Each of these calls requires your Amazon Seller_ID, Marketplace_ID, Developer_Account_Number,_Access_Key_ID, and your AWS_Secret_Key. Each also requires a SHA-256 hash of all this information along with the "canonical parameter list" If anyone wants my actual scripts, drop a note to me (At this moment, my scripts do the all-important /orders /list orders and /get order. I'm almost finished writing a /feeds filemaker API to send confirmations. I probably won't build scripts to manage inventory or subscriptions, but once you've built a framework for the scripts, it's not difficult to expand to more functionality) Best of luck all around, -Cliff Stoll
  47. 1 like
    Phil, if you have the means, I'd highly recommend the annual FileMaker Developer Conference. Nothing like a roomful of 1500 FileMaker developers to get you jazzed about the platform. They always include business sessions as well as technical. Also you should try to find a local FileMaker User Group. If there isn't one, start one -- use Meetup.com. That's a great way to get new business. I've been out of the consulting business for a while now -- but I do make my living as a full-time FileMaker developer for Oregon Public Health.
  48. 1 like
    Still very much alive and kicking.
  49. 1 like
    Try ExecuteSQL ( " SELECT COUNT ( NoteImportant__lxt ) FROM JOB WHERE CompanyName__lxt = ? " ; "" ; "" ; CompanyName__lxt ) To get this result from the context of Jobs without finding/sorting, create a summary field Count of NoteImportant__lxt and a Jobs self-join by company and display the related summary field from the self-join. As an aside: shouldn't you have (and use) a company ID foreign key in Jobs, rather than the name?
  50. 1 like
    Here is a working version of the EAN-13 barcode example. There was an error in the divider bar calculation. To see how to implement this code in existing solutions, see the upcoming UPC-A example in this Forum. Since the solutions are working now, I will delete all intermediate uploads. CodeEAN13new.zip
This leaderboard is set to Los Angeles/GMT-07:00