Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About TJ53

  • Rank

Profile Information

  • Title
  • Gender

FileMaker Experience

  • Skill Level
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
  • OS Version
    El Capitan

FileMaker Partner

  • Certification
  • Membership
    FileMaker Business Alliance

Recent Profile Visitors

2,196 profile views
  1. Hi, I have the Troi file plugin installed (FM 13 Windows 7 Home) and when using the "select folder" function the network drives don't show as selectable. This works well with Mac though. Since I thought it was something wrong with the plugin, I installed Base Elements plugin and used the equivalent "select folder" function. Same result, the network drives are not visible in the select folder dialog. Then I installed FM 14 in the same machine and the problem disappears: with the Troi plugin function "select folder" the network drives appear as selectable and folders can be created using the plugin in that network drive. Any clue why this can be happening? the only thing I can think of is (I believe) FM 13 is 32 bits on Windows but FM 14 can be installed for 64 bits. Any help is appreciated, thanks!
  2. PSOS Export Records Error 800

    Thank you very much! that was it, I just learnt about that and was about to post it here... I changed it to export as xlsx and it works perfectly.
  3. Hi, I get error 800 in the "Export Records" script step when executing it as PSOS. The file path is set in a variable ($path) as a calculation: Get(TemporaryPath)& "tmp.fmp12" This script works well when executing it to save the file to the local temporary folder (OS X El Capitan), but returns an error when executing it as PSOS (Windows Server). I believe it can be a permissions issue, but I thought the temporary path was accesible from FM Server "by default". Anyway, any insights are appreciated, thanks!
  4. Is there a way to use JSONPath with FM JSON functions? it would be great if I could use wildcards.
  5. Thank you! the exit script (false) on record commit script trigger comes handy for this situation. Thank you for the tip about GTRR, I was thinking on a situation where the portal record needs to created or updated from different contexts.
  6. I guess people are using a similar technique for creating and editing portal records after the new FM16 card window feature, any posts or links about this? In any case, this is how I'm doing it (sample attached) ... any feedback appreciated! Create or edit portal records.fmp12
  7. Virtual list using JSON

    That's some great information to take into account, thank you!!
  8. Thank you for the tip! I'll definitely keep it in mind.
  9. Virtual list using JSON

    Thank you for the responses, I hadn't thought about the speed factor, it makes a lot of sense. So ... are the JSON functions slow for building or parsing? I haven't tested them with big chunks of text. I see that in the recent FM16 update the speed of the "sort values" and "unique values" functions have been improved. Is the speed of the JSON functions an issue in a similar way? I haven't read anything about it ... any interesting links about this? thanks!
  10. I just did! looking forward to some replies Done!
  11. Virtual list using JSON

    On a separate thread I asked Bruce Robertson if the new FM16 JSON functions could be used together with the virtual list technique he created. I haven’t experimented with it but I wonder if JSON adapt well to this great technique. Any thoughts? thanks!
  12. Sounds good! looking forward to that.
  13. Thank you very much Bruce for your modifications, it looks good and crystal clear. I think it's a good philosophy you mention, I´ll definitely take it into account. I guess I often try to minimise the number of lines of codes and make my scripts modular, but I understand your point that this sometimes this goes against readability and easier debugging, I'll definitely look into that! By the way, I've been using your virtual list technique and I would like to take this opportunity to thank you for such great contribution to the community. I guess this belongs to a different topic but ... would your technique benefit if adapted to be implemented using the new FM16 JSON functions?
  14. Thank you Laretta. Please see attached example of what I'm doing. The idea is to try to workaround the scripted sorting limitation of FM by naming fields in the layout and passing the name as parameter. Actually, if FM had a script step "Go to Field By Name", the parameter passed could just be GetFieldName ( field_for_sorting ), and having to name the objects in the layout could be avoided. This is another limitation of FM scripting ... we have "Set field By Name", "Go to Object (object name as calculation)", but we don´t have "Go to Field By Name" ... Anyway, please let me know what you think about how I'm doing this ... I just want to avoid a bunch of "if - else" statements ... any suggestion is welcome, thanks! Sort_by_field_object_name.fmp12

Important Information

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