Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Junior360Works last won the day on October 13 2020

Junior360Works had the most liked content!

Profile Information

  • Title
    Apprentice Software Developer
  • Industry
    360Works, FM plug-ins

FileMaker Experience

  • Skill Level
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
  • OS Version
    High Sierra

Recent Profile Visitors

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

Junior360Works's Achievements


Contributor (5/14)

  • First Post
  • Collaborator
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges



  1. Hey Francisco, The quickest way to figure out what's going on would be to get a hold of our plugin logs for a user that is experiencing this issue. Assuming your scripts are being called client-side and users have the plugin installed, we would want one of them to send us logs immediately after getting that pop up. Our logs document plugin functions as they're being executed, so by examining the order in which functions are being called, we should be able to figure out the problem. Usually when we see this error, it indicates that you're trying to perform outgoing e-mail functions before actually connecting to your outgoing mail server. If the plugin functions are scripted to work on server, then please send the logs file you see in the ../FileMaker Server/Logs/360Plugin Logs directory to support@360works.com. I'll attach documentation users can leverage to send us logs automatically. If they go through the automatic workflow, please have them include your name and email in the bug report so we'll know to respond to you. If you end up sending the logs manually, please send them directly to support@360works.com and we'll take a look. Please make sure the issue is reproduced immediately before sending logs to ensure we're capturing the error. Automatic Log Sending: http://docs.360works.com/index.php/Send_us_logs Manual Log Retrieval: http://docs.360works.com/index.php/Plugin_log_files Thanks, Junior Perez 360Works Developer
  2. Hey Eric, The Rich Text Editor Addon by Claris uses HTML tags to create the rich text features, much like a WYSIWYG text editor (eg, QuillJS). If you look at the raw contents of the field you're editing with the addon, you'll see html tags everywhere you make any formatting changes. It's still entirely compatible with our Email Plugin, you would just want to make sure to switch the body-type from plaintext to html in any plugin calls. For instance, assuming you're using EmailSetBody to attach your body text while generating an e-mail, make sure to switch from the first step to the second. EmailSetBody( Email::body ; "plain" ) // this is used for mail clients which don't display HTML EmailSetBody( Email::body ); "html" ) // HTML version with formatting Similarly, if you're using EmailQuickSend, make sure to wrap the body text in an <html> tag and the function will know to attach the body as HTML. Let me know if you have any other questions, Junior Perez 360Works Developer
  3. Hey there, Do you know what version of MirrorSync you are running? If you are using MirrorSync4, try installing this dev version: http://sc.360works.com/SuperContainer/Files/pro/360/NewMirrorSyncBuild You can run the installer and it will update your MirrorSync software without touching your configurations or sync data. Once the install finishes, download a new config client and try to reproduce your issue. Hopefully, if you're still having issues, you'll at least be able to submit your logs to us. If the bug reporting feature still isn't working, can you manually send us your logs? They're located in the following directory: /Library/360Works/Applications/logs We're looking for files that start with the name of your MirrorSync installation (most likely, "MirrorSync") followed by a Date stamp (eg, MirrorSync.2018-07-15). Pick the one corresponding to the day you experience these errors. You can send the file to support@360works.com and we'll help to figure out what the issue is. Good luck, Junior Perez
  4. Hey Iain! Could you please submit your 360Works plugin logs to support@360works.com? I omitted your screencapture for security concerns. Here's some documentation on how to get to our plugin logs on your machine: http://docs.360works.com/index.php/Plugin_log_files Thank you, Junior
  5. Hey there, The best way to troubleshoot customization scripts is to run them while on the layout you are filtering using the data viewer and script debugger. This can often help identify what's going on behind the scenes that is causing your scripts not to filter the way you want them to. If you'd like, if you are still having issues after debugging, shoot me an email and I'd be more than happy to discuss what's going on. My email is junior@360works.com. Junior Perez 360Works Support
  6. Hey Stickybeak, SetErrorCapture doesn't exist as a script step, just as a calculation. Not all of our functions could be ported from calculations into script steps when FileMaker 16 came out, but they can be still be invoked just the same. Try the following line towards the beginning of that script: Set Variable [ $setErrorCaptureOn ; ScribeSetErrorCapture(true) ]; Here's a link to our documentation that describes the function in more detail: http://static.360works.com/plugins/Scribe/documentation.html#ScribeSetErrorCapture I hope that works. If not, please reply to my e-mail and I'd be more than happy to set up a meeting tomorrow. Junior Perez
  7. Hey there, Basically, when using XML, MirrorSync relies on the script steps to perform operations. When using JDBC on a server to server sync, I believe our script steps aren't being utilized at all as all communications occur over JDBC. However, for a Server to Pro/Go configuration, we do rely on script steps to hit FMPro/Go solutions (while using JDBC between the Server and MirrorSync). If your sync is server to server, then you can ignore the inability to copy and paste these steps. Otherwise, we do have to respect that restriction. It's a limitation imposed by FileMaker as to how many steps you can have in one script. I'll see about modifying that prompt to provide a little more information on the nature of script steps' max capacity and MirrorSync. I've known of customers who also opt into breaking their configuration into 2 smaller configurations, though this can be complex. You'd have to make sure the tables in each configuration were not related to tables in the other configuration, as otherwise conflicts can occur. It's not a strategy we currently support, though I've seen it work. Hope this answers your question. If you want more clarification or want to pick our brain about something, please don't hesitate to email or call us at support@360works.com / 770.234.9293!
  8. Hey Rick, What version of MirrorSync are you using? Would you mind updating to this version: http://sc.360works.com/SuperContainer/Files/pro/360/NewMirrorSyncBuild, and then giving it another shot? Also, what version of FMGo are you using? If that update doesn't work, please shoot us an e-mail at support@360works.com or call us at 770.234.9293 and we'll get this figured out. Junior Perez
  9. Hey Christian, We recently identified that with the latest version of Excel, whether it generates a file or seemingly just touches it, the file becomes unloadable by Scribe. I'm assuming it's manipulating the file formatting in a way that causes our plugin to not be able to parse through it correctly. Our Scribe developer is aware and will be working on this issue. I'll post back on this Forum when we come up with a fix. If you'd like, please shoot me an email (jperez@360works.com) and I can alert you directly when everything's been resolved. Thanks for bringing this to our attention. Junior Perez
  10. Hey David, Please e-mail me at jperez@360works.com and we'll get your issue taken care of. We're also open right now (10a-6p Eastern Time are our hours) so if you're able to call, please do. We can be reached at 770.234.9293, or if you'd rather Skype I'll provide that information via e-mail. Junior Perez
  11. Hey, Deploy will always move the development file to the production server, followed by a record import to make the dev file your new production solution. If you just want to import records from one solution to another, I'd suggest just using the native FileMaker import function to accomplish this. There's not a manual way to trigger just the import process in Deploy.
  12. Hey there, I'm interested in knowing who your hosting provider is, what version or MirrorSync they're using, and a little bit about your setup. Assuming we haven't already resolved this issue, would you mind emailing me that info at jperez@360works.com? I'd like to see your logs to get at the bottom of this and we may end up reaching out to your hosting provider. Thanks! Junior Perez 360Works Support
  13. I believe we've seen this and its fix is being incorporated into our next Plastic update. Our developers are working on the update now and I expect it to be out soon. I'll be curious to see if we see this error is the next release (Plastic 3.09). Thanks for bringing this to our attention. I'll make a general post when the release is out.
  14. Hey Nightwalker, Based on a little digging I did, I get the impression this prompt you're seeing is related to a feature in Office365/Exchange software allowing users to relay e-mails on behalf of other users. I'm guessing that somehow the way this user's account was configured doesn't allow them to succeed with the task they're trying to execute. I don't get the impression this is related to the 360Works plugin. If you want me to take a closer look, or would like to have a developer take a look at this and see what they suggest doing to fix this, by all means please reach out to us at support@360works.com and we can work something out. Good luck, Junior
  15. Hey there, That should do the trick. It appears as though the complaint our plugin had was with null being passed as a parameter, meaning it wasn't being set at all. I'll talk to our developer in regards to whether TestMode should default to a value if not set, or provide some error prompting indicating the issue in plain language. Thanks for bringing this to our attention.
  • Create New...

Important Information

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