Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


sean360Works last won the day on August 7 2019

sean360Works had the most liked content!

1 Follower

FileMaker Experience

  • Skill Level
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
  • OS Version
    High Sierra 10.13.4

Recent Profile Visitors

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

sean360Works's Achievements


Enthusiast (6/14)

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

Recent Badges



  1. Hi David, Could you please download and install the latest store build of Scribe to see if that resolves that behavior. I reviewed previous support tickets, and we resolved a similar issue recently where processing Excel and Word documents produced a NullPointerException. This version of Scribe is 4.0726, and can be downloaded from our webstore by going to the link below and clicking "Download current version". https://360works.com/filemaker-pdf-plugin/ If you are running the latest build of Scribe and are producing that NullPointerException, could you please locate the plug-in log file and email it to [email protected] along with instructions on how you produced that error? You can reference our documentation at the link below to locate the plug-in log file. http://docs.360works.com/index.php/Where_to_find_logs If you have other questions, please email them to [email protected] and we can reply to you more promptly through our ticketing service.
  2. Hello, In FileMaker, you can use functions where you can specify a Calculation. Typically, users implement the function in a Set Variable script step so that they can trap for errors during scripting---our functions will return 1 on success and "ERROR" if the call fails---or for retrieving information like file paths, depending on what the function is designed to do. By calling the plug-in function instead of the script step, you will be able to add additional arguments to the function call. For example, you can call ScribeDocWriteValue() with a list of arguments to write an image to a file at a specific position and with specific dimensions. If you wanted to write an image stored in container field MyTable::MyImage to the first slide of a loaded powerpoint file at coordinates (100,200), set the image width to 300px and the height to 400px, you would call ScribeDocWriteValue inside of a Set Variable script step as follows: Set Variable [ $result ; ScribeDocWriteValue("1"; MyTable::MyImage;"x=100";"y=200";"width=300";"height=400") ] If the call is successful, variable $result will have value 1. Let me know if you have other questions.
  3. Hello Leland, The path in the link you provided is different from the one we expect. https://360works.com/article-detail/391 Thank you for bringing this to our attention. We'll work on implementing a redirect for that old path. Also, let me know if this is not the resource you're looking for.
  4. Hello, You will not be able to pass in additional key-value pair parameters into ScribeDocWriteValue as a script step. If you want to pass in more parameters, please use ScribeDocWriteValue as a function instead.
  5. Hello Noël, That's great to hear, and thank you for letting me know!
  6. Hello Noél, Please close FileMaker and delete that entire 360Works directory containing the path and JRE file(%localappdata%/360Works/). If you're using Windows, make sure the correct bit-version of the plugin is installed in the FileMaker client Extensions directory(64-bit FileMaker Pro Advanced will require plugin with extension .fmx64). Upon initialization, the plugin will detect the missing JRE and attempt to download and install it. This will ensure the correct JRE is installed for the plugin. If it fails to download, you can follow the instructions in the documentation you linked to download and install the correct JRE. Again, if you're running FileMaker on Windows, make sure you match the JRE bit-version with that of your FileMaker client. Let me know how that goes or if you have any questions.
  7. Hello, By "if the first record completes, then the script sets the related from 0 to 1", do you mean you have a subscript call configured in the customization section of the MirrorSync script? or are you saying that as the MirrorSync script executes, changes made by the sync adjusts those auto-enter values? It sounds like the cause of the record state discrepancy is variability in the records' states during the sync. Since the auto-enter is allowed to trigger whenever a related record's field changes, and the value is dependent upon another record's status, the order the records sync could affect the record states. Also, Auto-Enter calculations are one of the last fields MirrorSync writes to when inserting/updating a record, so if the auto-enter field is included in the sync, and the calc result is different from the value MirrorSync picked up from the spoke, MirrorSync will end up overwriting the calculation result with the value from the spoke file. Is that field used for customization? Does it determine which records are included in the sync?
  8. Hello, Could you please provide more information about the sync? What is the field definition for that field? Is the table containing that field configured to sync data in both directions or just one direction, and if the latter, which direction? Are you applying customization to filter what records sync? What is the "record lock" workflow you mention?
  9. Hello, This is expected behavior. The FileMaker Data API requires that you log into the database https://fmhelp.filemaker.com/docs/18/en/dataapi/#protect-host-solutions -> Prepare databases for FileMaker Data API access -> Protect your FileMaker Data API solutions In your sync configuration, if you are selecting the option to use FileMaker credentials to log into the hub database, you will need to set passwords for user accounts that want to sync. If users have the same access to records in the database as a Full Access account, you can set it to use hub credentials when logging into the hub. The hub credentials should be for a Full Access account, and a Full Access account requires password-protection in solutions hosted on FileMaker Server 17+.
  10. Hello, Yes, you should be fine syncing a FileMaker with SQL server. The documentation section you included in your post is referring to fields like 'modified timestamp' and 'modified by' that update automatically anytime a field in a record changes value. You should only include the modification timestamp field in your sync configuration. To clarify, syncing modification fields other than the timestamp will produce conflicts because the data will likely update to values different from what MirrorSync writes to the records. Since MirrorSync is unaware of any other modification fields beyond the timestamp, any data discrepancies between what MirrorSync has written and what exists in a database will be processed as a conflict, which will slow down sync performance, and possibly compromise data integrity. The reason you can include the modification timestamp is that MirrorSync references that specific field when evaluating record updates, and it is the only modification field MirrorSync can account for because it is specified in the sync configuration. Other fields you will want to exclude from the sync layout are calculation, summary, and global fields. MirrorSync cannot write to calculation and summary fields. Global field values are specific to the database sessions---their values should not persist.
  11. Hello, I apologize for the late reply. Are you still experiencing this issue? If so, please submit a MirrorSync log to us. This can be done through the MirrorSync launch page where you downloaded the configuration client([server address]/MirrorSync) by clicking the link Send Problem Report and Log Files, filling out the form, and submitting. If the behavior occurred on a day different from when you are submitting the log, then change the log date on the submission form to the day when the behavior occurred. If that date is more than 2 weeks prior to the current date, you'll have to reproduce the behavior, then submit the log for that day. When we have seen this error in the past, it was either because the container field was set to store a file as reference---not store externally as you stated---or the user under which the sync was executed had restrictions applied to the account preventing proper access to the sync layouts. Please check if either of those may apply.
  12. Hello, It is possible to change the background color of a cell. To format the background color of a cell, you need to specify three arguments in the ScribeDocWriteValue call: 1st: cell name 2nd: color 3rd: "background=true" To change the background color of cell H4 to green, you would call ScribeDocWriteValue( "H4" ; "green" ; "background=true").
  13. Hello, Sorry for the late reply. Could you please reproduce the behavior and submit a log file? You can do this from the MirrorSync launch page where you downloaded the Configuration Client([server address]/MirrorSync) by clicking the link Send Problem Report and Log Files, filling out the form, and submitting. Please include in the form body the behavior you're seeing, the layout of the table where the new record is being generated, and the primary key value of that new record. Is the Project layout built on a table that's included in the sync? If not, the MirrorSync script should not be inserting any scripts into that table. Are you applying any customization or post-sync scripts? If the table is included in the sync, I'll need to check the log for activity associated with that particular record whose key you include in your log submission.
  14. Hello, I apologize for the delay in response. You cannot get header information from emails you are sending, only emails that are in your mailbox. You could possibly move the email to your Sent folder after sending, connect to your email server via IMAP/POP, then pull that email into FileMaker while calling EmailReadMessageValue("headers") on it to get the headers after it's been sent.
  15. Hello, I apologize for the delay in response. What specific fields are you asking about? Are you asking about the modification timestamp fields set for each table that are mapped in the sync configuration? If so, these fields are important for MirrorSync to determine which records have changed state, and what values to update on each side of the sync. MirrorSync maintains sync data against which it compares the modification timestamps to evaluate the latest record states. In the case of automatically merging fields, the modification timestamps are important to MirrorSync deciding which fields should be copied from the hub to the spoke, and vice versa. Please let me know if that does not answer your question, or if you have more questions.
  • Create New...

Important Information

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