Jump to content

naio

Members
  • Content Count

    74
  • Joined

  • Last visited

  • Days Won

    1

naio last won the day on March 2 2020

naio had the most liked content!

Community Reputation

1 Neutral

About naio

  • Rank
    always learning

FileMaker Experience

  • Skill Level
    Intermediate
  • FM Application
    19

Platform Environment

  • OS Platform
    Mac
  • OS Version
    Catalina

FileMaker Partner

  • Certification
    Not Certified

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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
  3. 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.
  4. You're absolutely right, I'm discovering the world of JSONSetElement with brackets, already got rid of that JSONFormatElement... Thank you,
  5. 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!
  6. 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 w
  7. 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.
  8. 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.
  9. 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}" ) an
  10. 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?
  11. 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.
  12. 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.
  13. 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 u
  14. 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.
  15. 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
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.