![]() Select the plugin from list (highlight the line).If you are using a plugin in FileMaker Pro, then you can use the Send Bug Report feature to send us the plugin logs and also create a ticket in our support system. If you need help submitting for non-plugin products (tools such as MirrorSync and Zulu), please see the bottom of this page. It is the same set of instructions for any plugin you use. These instructions are for submitting a bug for ALL plugins, including but not limited to: Scribe, Email, CloudMail, Plastic, FTPeek, JDBC, Charts, Web Assistant, ScriptMaster, and SuperContainer Companion Plugin. If using the automated process, you do not need to send an additional email as the automated process will create the ticket for you as well as attach the logs. If the automated process does not work you will need to send the logs manually. Some products have an automated way of sending the logs while others will require that you manually attach the logs to an email. This will vary depending on what product you are using. Sending these with your initial email will expedite the support process. ![]() Additionally, it is common for us to request logs in order to troubleshoot the issue. It will help if you include the operating system, version of FileMaker, the product and the version of it this issue pertains to and steps to reproduce the issue. If I get to working on this I will post an update here or add a new blog entry.If you are experiencing any issues with 360Works products, we may ask you to submit a ticket by sending an email to In the email, be sure to include as many details as possible. ![]() The HTML specifications technically define the difference between “GET” and “POST” so that former means that form data is to be encoded (by a browser) into a URL while the latter means that the form data is to appear within a message body. Another approach might be to employ one of the plugins that can do HTTP POST commands, such as Scodigo’s SmartPill ($89 single user license) or 360Work’s ScriptMaster, (free) might be required.Ī reminder of the difference (I forgot exactly as well) between GET and POST is: You might need to run this off FileMaker Server and use PHP to send and receive the interchange between FileMaker and Constant Contact. It looks like Constant Contact is mainly using POST commands. (ie put everything in a URL and throw it at their server, get back JSON or XML). MailChimp allows everything to be done using GET commands. I haven’t explored Constant Contact fully yet, although another one of my clients has talked about wanting this as well, so I may get to it sooner or later.Ĭ‘s documentation for their API is here.įrom a brief scan of their API docs, it sounds like you could do something similar, although it does not appear to be quite as streamlined. Then to do simple updates, adding people to groups, taking them out of the list, or adding a few new members, this can all be done using the WebViewer/Parsing techniques. The batch export/import is going to be the preferred mode to get set up. You will probably only want to employ the technique to add a few new subscribers at a time. Using the Web Viewer/Parsing method we described in Part 1 of this article is very useful, but to be honest it is a tad slow. Using a batch export/import routine is the best approach to dealing with large numbers of subscribers. We also built an Export script to send larger batches of email addresses to MailChimp. The MailChimp API Methods we have chosen to support in this demo include: Subscribe and Unsubscribe from a List Add/Edit/Delete Groups Get info on Lists Get info on Groups. We are not trying to do that, but rather, show a set of fairly straightforward techniques to allow you to keep your two data sets of email address in sync. Using the basic technique described here, you could create campaigns and start your emails right in FileMaker. We are not attempting to replicate the complete MailChimp API, which is extensive. Keeping the records in FileMaker and MailChimp in sync is the object of this demo. Using the techniques in the sample database, we hope to display an approach to keeping the two ‘data islands’ a little closer together. ![]() Changes made directly to MailChimp may not show up in your main system and vice versa. As soon as you create another data table of your email addresses, the records can start to drift apart. The problem of working between two system (FileMaker and MailChimp), is the issue of data islands. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |