naio

In my multi platform solution, I want to save a pdf file to the user Downloads folder in any of both OS, so I've set up this variable: Case ( Get ( SystemPlatform ) = 1; "filemac:"; Get ( SystemPlatform ) = -2; "filewin:"; "" ) & Substitute (Get (DocumentsPath); "Documents"; "Downloads" ) & docs::docName & ".pdf" It works in Mac but in Windows 10, I get an error saying: "docName.pdf" can't be created in this disk. Is this a Windows disk permissions issue? it can be fixed?

Thank you, it looks very interesting but a bit overkill for my needs.

Thanks for letting me know. DMT Must be one of the most opaque applications I've ever used. I'm using FM 19.3.2.206 and I wonder if DMT 19.3.1 is compatible with files created with that FM version? anyone knows where can I find this info?

Ok, I guess they were too busy to let me know that my membership doesn't allow access to that page. I'm just very curious about the content of that article, do they describe each of the DMT versions released? do they state the compatibility with each file version? If you can enlighten me I would be grateful...

I don't see it this way, I'm logged in to https://community.claris.com/en/s/ I see a message saying "Welcome back", I can read articles but when I try to access the link you sent I cannot, I get a message like saying page can't be found. Maybe is a different membership that I need? However I've found this article https://community.claris.com/en/s/article/New-FileMaker-data-migration-tool which has exactly the same content of your first link, here including a discussion thread. If there is an article with additional and valuable information about DMT I'd appreciate you send me the link. Thank you in advance.

Broken link: https://community.claris.com/en/s/article/FileMaker-data-migration-tool

I understand that an independent developer gets a lot in the FileMaker Developer Subscription (that' where DMT is included) but in my business I develop my own solutions, so I already pay for 1 FMS license and 3 FM licenses, IMHO that should include the DMT. The subscription license is an additional 10% to the cost of the whole license package and all I get from it is DMT. Anyway, I already paid once for the subscription, but I wonder if an old DMT works well with the current FM version. I couldn't find a DMT release history and that's quite poor from Claris: they force you to pay $99 for a software you don't even know it will work with your files. My question is: does Claris expect me to buy a new FDS every time it releases a new software version? or should I assume that DMT will work with any fmp12 file? And is this explained somewhere?

Thanks for your reply, it's not that I didn't think about your suggestion but the latest version is sold bundled with a lot of stuff I don't really need, and it's not cheap.

I have FMDataMigration version 17.0.1.143, I haven't used it since long ago, do you know if it works well with files created by FileMaker 19?

My solution is hosted in FMS on a Mac and there are a couple of Windows 10 clients. Some layouts include container fields set up to display PDF files (optimized for interactive content). Those pdf files are stored externally in the server but clients run the solution through a local file. Under Mac it's all right, but under Windows 10 it's a nightmare: it happened before, suddenly those PDFs don't display and it all seems caused by a software update (I can't tell if it's Windows 10 or Adobe Reader). The error message comes from Reader: "There is a problem with Adobe/Reader. If it is running, please exit and try again. (507:507)" it is not running alone, only through FileMaker. I remember once I fixed it by downgrading Reader to an older version but this time it doesn't work. So I thought of displaying them through a web viewer instead of a container field, I set it up this way: "data:application/pdf;base64," & Base64Encode (myFile::pdfContainer) This works in Mac but not in Windows, I conclude that there is no difference between using a web viewer or an interactive container, the problem seems to be Adobe Reader. Do you know of a robust solution to display those PDF files stored in container fields in Mac AND Windows?

Finally, after a couple of weeks researching, I've got a reply from FileMaker Support: it's a bug in FMS, it happens with a hosted file related to another hosted file using fmnet:. The workaround is to use file: instead, however this prevents to have the external file in a sibling folder.

I've tried to reproduce the issue with a brand new file: I've made the same relationship with the problematic 'not-properly-sorted' field which is hosted in FMS. When I created the new file in my machine, sorting worked as I expected. Then I uploaded the new file to FMS, and sorting didn't work (at least not the same way as local), as you can see in the enclosed screenshots: Local file, the 'id' field was filled as records were created. In the first image it is unsorted in the second is sorted by the 'engagement' field, it looks all correct. The file now hosted and sorted by the 'engagement' field only, please note the sorted icon in the column header: FMS hasn't found any problem after verifying both hosted files. You're right about the difference of expectations between me and FileMaker, it happens very often , but you'll agree that sorting should work exactly in the same way regardless of the file being local or hosted, otherwise I'd love to learn why.

It's been a while for me using FM, I've always sorted records by a related field and got records sorted without problem. Today this doesn't seem to work, execute 'Sort records' changes the initial sort order but they don't get properly sorted. This is happening in table view with records from two files hosted in FMS. Any idea of why this may be happening? Thank you in advance.

You're absolutely right, I'm discovering the world of JSONSetElement with brackets, already got rid of that JSONFormatElement... Thank you,

Oops! you are right, actually those characters are in the source data but invisible within FM. Regarding the use of JSONSetElement: I think that, for large JSON objects, JSONFormatElements avoids the nesting of several JSONSetElement functions. Anyway I'll consider your advice. Thanks for your help!

The content of myField is: text before quotes "quoted text" and I want to format a JSON object: JSONFormatElements ( "{\"object\":\"" & myTable::myField & "\"}") the quotes within my data make invalid JSON, so I escape quotes: JSONFormatElements ( "{\"object\":\"" & Substitute ( myTable::myField; "\""; "\\\"") & "\"}") Then I get valid JSON like this: {"object" : "text before quotes \"\u0016quoted text\u0016\""} I wonder where these \u0016 characters added around the quoted text come from, I don't want them there How should I escape quotes without this problem?

This issue seems related to Windows 10 file permissions because I've tried to run the script under a windows admin account and it worked well, so it doesn't look like a FileMaker problem but I'm completely lost. jaboda: Thanks for the filewin tip anyway.

My script in a hosted file needs to export records as pdf into the user Downloads folder, needs to run under Mac and Windows, so I set the variable $path_filename to: Case ( Get ( SystemPlatform ) = 1; "filemac:"; Get ( SystemPlatform ) = -2; "filewin:"; "file:" ) & Substitute (Get (DocumentsPath); "Documents"; "Downloads" ) & "file.pdf" And then: Save Records as PDF [With dialog: Off; $path_filename ; Records being browsed ; Create folders: Off] The script it works in Mac but not in Windows: I get an 800 Error and a message warning that it can't create the file. I don't get what's wrong with the windows version, any idea?

Again, another picky API: https://developers.sendinblue.com/reference#updatecontact With this PUT command, I can't find the way to send the --data parameter to the server. These are the cURL options I'm using: --request PUT \ --header \"accept: application/json\" \ --header \"api-key: " & $$my_api_key & "\" \ --header \"content-type: application/json\" \ --data @$parametre I've tried to set the $parametre variable to: JSONSetElement ( "{}" ; "emailBlacklisted" ; True ; JSONBoolean ) JSONFormatElements ( "{\"emailBlacklisted\":true}" ) and simply: "{\"emailBlacklisted\":true}" none of these options satisfies the server, which always returns the following error message: {"code":"bad_request","message":"Input must be a valid JSON object"} There may be something wrong in the syntax of the --data parameter but I can't find what it is. I've also tried to quote the parameter: with single quotes --data '@$parametre' and escaped double quotes --data \"@$parametre\" None of this seems to work. I'm completely lost...

I have a master table that needs to calculate the total value from many fields in a related, child table. The total must be shown –not necessarily stored– in the master table layout. I wonder what's the best option: Create a non-stored calculation field in the master table with Sum (child::value) or Just display a child table summary field with the total of child::value Both options seems to work but I would like to know if there's any difference in performance, is option 2 better than 1?

I didn't mean import into another file but import between tables in the same file, so shortening the "export/import" process. Export to temporary folder and importing afterwards is fine, at least in csv format.

Although I haven't read it in any documentation, it seems that FileMaker Server cannot handle self imports, so I had to export and import to and from a temporary file.

I have a file with 2 tables: updates on table A are imported into table B using the update matching records option based on a common id. I made the script and tested it without problem. Then I uploaded the file and scheduled the script to every x minutes. The script executes with full privileges. The scheduled execution seems to skip the import update, so table B never gets updated. The most surprising is that the script works as expected when executed manually but it doesn't do the import update in scheduled execution. I can't see any error code. Is this normal? I'm using FMS 19.0.1.103

I've tried with my non-formatted json data (as in my first post) but now excluding the single quotes around it and it doesn't work, maybe the API doesn't use a non-conforming parser, I can't tell. For debugging this I used the very useful tool offered by Mike Duncan here: https://www.soliantconsulting.com/blog/filemaker-rest/ and I see FM is not sending non-formatted data.

I've found the problem: json data must be formatted with JSONFormatElement, so the cURL option in FM must be: curl -v -u <user>:<password> --header "Content-Type: application/json" --data @$json_parameters -X POST Where $json_parameters is a FM variable that stores the value of JSONFormatElement