Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


nick360Works last won the day on February 7 2020

nick360Works had the most liked content!

Community Reputation

5 Neutral

1 Follower

About nick360Works

  • Rank

Profile Information

  • Title
    Apprentice Developer
  • Gender
  • Location
    Atlanta, GA

FileMaker Experience

  • FM Application

Platform Environment

  • OS Platform

Recent Profile Visitors

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

  1. Marc, Thanks for the update, and for sending in the file. Please let us know if you need any other assistance.
  2. Marc, Could you please send an email to our support email support@360works.com with a copy of your document, so I can run some tests on it. I can then send you a demo database that runs the substitutions for you as an example. Nick 360Works
  3. Hi Marc, Thanks for explaining the issue clearly. It looks like your script and logic are fine. The issue may be with the file itself. Scribe requires Microsoft Word (2007 or later) for the .docx format. You may need to save the file in a more current version of word. You can also try using Scribe on some different .docx files, and see if they are triggering the same error. What version of Scribe are you using? Nick 360Works
  4. Markus, Apologies, that information is only pertinent in cases where the deletions occur in FileMaker. Since your setup is a server to server, with your SQL database as the spoke, there is no way to selectively disable records from hub to spoke. One alternative is to disable deletions entirely in the MirrorSync.xml file. That way, when hub records are deleted, the records would remain in SQL. You can locate that file at the following location: /Library/360Works/Applications/webapps/MirrorSync/META-INF You would then modify the following parameter to a value of "never":
  5. Hi Markus, Thanks for explaining your setup clearly. This is something that can be easily accomplished using the MirrorSync Customization Script, which is now a part of the MirrorSync Script in MS 6. In the "WillDelete" / A RECORD WILL BE DELETED ON THE HUB section of the script, you can constrain your found set to omit and filter out which records you want to be deleted. Therefore, you could limit your deletions only to records that are marked in a certain way (ie, existing records only) that you would want to be deleted. Unfortunately, specific MirrorSync customization falls o
  6. Hi Crawfcol, It seems like the related table and fields that the Portal Row is associated with is not set up to be synced. Because the records from the Portal are coming from a different table than the one that is syncing, you'll need to make sure that related table and the fields that you want to sync are set up in your MirrorSync configuration to be synced. MirrorSync doesn't really care about the portal, it just needs to know that you want to sync records from that related table, and the relationship between the two tables. After checking your MirrorSync configuration, and it
  7. Hi pfroelicher, Zulu has functionality built in to handle recurring events. Instead of having many large multi-day events, you can create "recurring events" that occur based on any time or day interval. Please refer to our Zulu documentation on that subject at the following link http://docs.360works.com/index.php/Zulu_-_Recurrence . It is recommended that you create the recurring events on the non-FileMaker side of the calendars (ie. Apple Cal, Google, Exchange) as it is easier, but it is also possible to create the recurring event within FileMaker. There is a built in script in
  8. Hi Ocean, Yes, there are some overlaps between the two plugins, and there have been discussions on merging the two plugins together, but there are currently not any plans to do so. I am not aware of any advantages or speed differences between the two plugins, however, for any scripts you might write I would try to stick to one plugin to avoid loading and saving the documents between two plugins unnecessarily.
  9. Anatole, When multiple versions of FileMaker are installed on the same machine, there can be multiple locations where plugins can be installed. If any of those locations contain older versions of the plugins, they can cause framework conflicts between the plugins, and would cause failed initializations. Please check for plugins at: ~/Library/Application Support/FileMaker/Extensions ~/Library/Application Support/FileMaker/FileMaker Pro Advanced/16.0/Extensions Applications/FileMaker Pro 16 Advanced/Extensions Once older versions of the plugins are cleared out, the AutoUpdater
  10. Hi, I tested with our AutoUpdate, and was able to successfully install CloudMail 3.3 on my FileMaker Pro 18. Are you attempting to install the plugin locally on FileMaker Pro, or on FileMaker Server? Our plugins will write a temporary initialization log to the temp directory when attempting to initialize, please try to initialize the plugin, and then locate the log at: On Mac: check in /tmp for a file called 360Works_XXXX where XXXX is random alphanumeric string. On Windows: Open File Explorer and type %tmp% in the address bar. Look in that location for a file called 360Works_XX
  11. Hee, It looks like your max batch size may be limiting the number of emails being read. The number of records skipped could also limit some of the emails from being read. Since those values are coming from a field reference, you should run the script through the script debugger and see what values are being passed in the for the max and skip parameters.
  12. Hello Hee, This may be an issue with the script that you are using to read in the messages. If you are filtering emails with EmailReadMessages parameters, it may be restricting those new emails from coming in. Try reading the emails and modifying your read parameters. However, to know for sure I would need to take a look at your email plugin logs and your script. You can send in a plugin log and a screenshot of your script to support@360works.com. Here are the instructions on how to locate those logs http://docs.360works.com/index.php/Plugin_log_files.
  13. Hi Dave, Please open the 360Works admin.jar (/Applications/360Works Admin.jar or C:\Program Files\360Works Admin.jar), and click start for the MirrorSync service to restart it. Normally, MirrorSync should automatically restart when the Tomcat service restarts, however if that is not the case please follow the steps at the following link http://docs.360works.com/index.php/MirrorSync_5_advanced_topics#Starting_the_360Works_Tomcat_server_does_not_start_the_MirrorSync_application.
  14. Hi fmjv, As Wim has said, this change would ultimately be up to how Google decides to handle how Gmail connects with 3rd party software. There wouldn't be anything that could be done on the FileMaker side to connect with a service that is blocking access. That being said, please forward a copy of the email you received detailing this change to support@360works.com, and I will take a look at it to see if there any other changes that might let the service allow a connection. I will bring this issue to the attention of our developers, and hopefully we can find an alternative.
  15. Hi, Unfortunately, Scribe can only write to individual cells, so you would need to use something like a loop within your scripting to write multiple values quickly. This is due to the way Scribe writes to excel through XML.
  • Create New...

Important Information

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