julie@360works.com

Wonderful! I am glad to hear this has helped you. If you have any issue in the future, we are always happy to help. Thanks, Julie 360Works Support

Hello, Sometimes we see a message similar to that, and it can be fixed by either telling Google to proceed anyway, or by using the API Key set up I mentioned before. I would recommend going over that page, which again you can see here. If you have any issues with that set up, or are getting error messages, I would recommend submitting a problem report from the Zulu admin console in your browser. The logs that will be sent can often let us know see the responses from Google and help guide you on what needs to be adjusted. Thanks, Julie 360Works Support

I understand. Users can subscribe to Google calendars. How you want this set up changes if the students have a FileMaker app, or if they will be subscribing via Google. You can read about subscribing with Google here. Once you have Zulu set up to sync to your Google Calendar, you can have users subscribe through Google. It is not too different than subscribing in iCal, but it would be done through Google.

Hello, It sounds like you are having some difficulty setting up a Zulu to Google calendar sync, is this correct? Are you receiving any error messages? Google calendars in particular can require a little extra work to set up, as Google has recently changed their API and security systems. We have updated Zulu to accommodate the changes, however you may also need to set up an API key. We have instructions in our documentation for connecting to Google, which you can view here. We also have instructions for setting up the Google API Key, which you can view here. I hope this is helpful! If you are having further issue or receiving any error messages, I would recommend submitting a problem report from your Zulu Admin console, as log files are often the best way for us to assist you. Thanks! Julie 360Works Support

Hi, I have a build of Zulu I would like to get to you, Having an email to contact would be the next best step. I realize the report didnt go through. I'd like you to send an email to support@360works.com. Please write "For Julie- Zulu Support" in the message and my team will know to get that to me. Once I have your email I can send you a new build and we can hopefully make some progress. Thanks! Julie 360Works Support

Hello, The best way for us to work through this error is to see your log files. You can visit : http://docs.360works.com/index.php/Zulu_-_Email_Log_Files This page will guide you on submitting a bug report and getting you Zulu logs to our support team. Thanks! Julie 360Works Support

Hello, I'd like to get a clearer image of the behavior you are seeing. Please send an email to our support team with a short video showing the behavior, along with a log file from the same time. You can use the documentation at http://docs.360works.com/index.php/Plugin_log_files to help you find the log files. You can send the email directly to support@360works.com, or use our form at https://360works.com/support/ to contact us. Thanks, Julie 360Works Support

Hi Markus, It looks like you have the correct driver class name. You will need to get the jar file for the JDBC driver. You should be able to get the latest one here: https://jdbc.postgresql.org/ I believe this should resolve the issue. If you have any issues, I'd like you to submit a support ticket through our website. You can find that at https://360works.com/support/ Thanks, Julie 360Works Support

Hello, The thread you were looking at is a good bit older, so I would recommend submitting a log file to our support team to get to the root of the error you are seeing. First, recreate the error in FileMaker, then send in the log before you shut down FileMaker. You can use this documentation to help you find the log files on your machine: http://docs.360works.com/index.php/Plugin_log_files Send the log to support@360works.com and one of our support team members will be in touch. Thanks! Julie

Hi Jadzas, To give you the best answer, I would need to know a little bit more about your solution and set up. Are these files being stored in a folder on your local machine, or are they being stored in FileMaker as well? Are these two csv files being created daily, and do they get new names or is it the same two files just being updated? Are you trying to keep copies of every csv that is generated, or are you interested in removing them locally after they are uploaded? Are you looking to automate this process so it runs as a scheduled script, or will there be any user interaction with the file? These are all questions that change how you might go about this. In general, there is no single function that will automatically select the newest item in a local directory. You could make a solution that still selects and uploads the files, but there are multiple approaches and no one right/wrong way. For example, uploading from containers in FileMaker could be an easier solution for you. A scheduled script could look for the record based on creation/modification timestamp or a status field. Another potential method would be to have a temporary folder that only stores files generated that day/given time period, and have a script scheduled to delete the contents of the folder after uploading. There are plenty of other ways you could go about this, some more complicated and some less. These are just general ideas to go from. I feel quite sure you could ask 10 developers and get 10 answers of what to do, or for that matter not to do. I hope this is helpful. If you have any issues as you work with FTPeek, you are also welcome to email us at support@360works.com.

Hi Ian, It is probably best if you did not have pre-existing Creation Time Stamps and Modification Time Stamps to perform a calculation to fill in the fields for pre-existing records. Simply using the database is not necessarily going to fill those time stamp fields in. For example, if you have 100 records and during use you modify 50 of them, you still would have 50 records that do not hold information in their modification time stamp field, as they have not been modified. Generally, if you are using FileMaker tables are automatically generated with a Creation Time Stamp and a modification timestamp. If those are still intact, you could work with them. If you are not using a FileMaker solution for your server to server, or if you deleted those fields, you would need to make your own. I hope this is helpful information! If you encounter errors as you set up your sync, I would recommend submitting directly to our support team, either with email or a Problem Report. You can submit a problem report from your MirrorSync launch page in a browser, or you can send emails to support@360works.com.

Hi Gary, It never hurts to ask and be sure! It is the case of all value lists and user accounts that they will come from the prod file, not the dev file. It may seem a little strange, but this is the preferred method to protect your prod file's accessibility. You can make changes to value lists or user accounts in your prod file, and the next time you deploy those will be merged into the dev file as well, so that the dev file will then match the prod. -Julie

Hi Gary, I want to be sure I answer your question correctly. It sounds like you are able to locate the folder, but there is a permissions issue preventing you from accessing the folder. To set the permissions for a folder on a Mac, you can right click the folder. On the pop up menu, select "Get Info". On the new window that opens, there will be a lock in the bottom right corner. Click on the lock, and you will be asked to put in your username and password. This is not the 360Deploy username and password, this is your computer username and password. After this, you can use the menu at the bottom of the Info window to adjust the permissions to allow you to access the folder. I hope this is helpful. If you have any further questions please let us know. You can also submit a ticket to our support team from our website at https://360works.com/support.html -Julie

Hi Alan, I sent you an email with more details, but wanted to post here as well to be sure you receive an answer. 360Deploy can deploy one development solution to multiple production solutions, but you will need to be sure you have the correct licensing for your use case. For example, our Solution Bundle allows updated file versions for one solution to be deployed to an unlimited number of live / production servers and companies. The deployed solution can have different names. You can see more about this on our store at 360works.com, or I can refer you to our licensing department as well if you have any other questions. -Julie

Hello, The good news is that you can call ScribeDocAppend multiple times in a row without saving and reloading the master document. I think this would make your workflow much easier. You could easily have your assortment of optional sections saved to their own container fields, and have the substitutions performed to create the new sections. Then, load your master document and call append for your needed sections, however many times. Once you have finished the append calls, then save the final file. There are several ways you could handle this in your script, here is a simple example: If you have a master document and 3 optional sections to substitute and then append onto that master document, you could have six container fields for holding your templates. 1a, 1b, 2a, 2b, 3a, 3b. In the A container, load your original template. Loop through, performing substitutions, and saving the new/finalized sections in the B field. You now have your finalized sections in containers 1b, 2b, and 3b. At this point, ScribeDocLoad your master document, and call append in succession. Once all have been appended, save your new document. You do not need to save between appends, so it would look a bit like: ScribeDocLoad[Container or Url: Database::LoadMasterDocumentContainer] ScribeDocAppend[Data: Database::Container1B] ScribeDocAppend[Data: Database::Container2B] ScribeDocAppend[Data: Database::Container3B] ScribeDocSaveContainer[Select;Result: Database::SaveNewMasterDocumentContainer; New Name: "NewMasterDoc.docx" While this is obviously a simplified version of what you may be doing, I believe this sort of set up would save you some overheard and speed up your workflow. I hope this is helpful for your solution.