Jump to content


Productive Computing
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About PCIPal

  • Rank

Profile Information

  • Location
    San Diego County, CA, USA
  • Interests
    QuickBooks Integration, Outlook/Exchange Integration, FileMaker Hosting, FileMaker Plug-ins, FileMaker Custom Development

Contact Methods

  • Website URL

FileMaker Experience

  • Skill Level
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
  • OS Version

FileMaker Partner

  • Certification
  • Membership
    FileMaker TechNet
    FileMaker Business Alliance
    FIleMaker Platinum Member
  1. Pulling Received Payments from QuickBooks

    Hi Christi, It's possible that the evaluation of the request might be experiencing an error (such as a validation error or something of that nature), which would cause the response XML to still maintain the previous successful response, which would be the "all received payments" result. In that case, checking the result of PCQB_SGetStatus immediately after PCQB_RqExecute should show what is missing. I was able to successfully test pulling all received payments for a specific Customer and their Jobs using the following script (I used the "Sample Products-Based Business" company file available in QuickBooks 2016): PCQB_RqNew [Select; Results:$result; Request Type:"ReceivePaymentQuery"] PCQB_RqAddFieldWithValue [Select; Results:$result; QB Field Name:"EntityFilter::FullNameWithChildren"; Field Value:"Jacobsen, Doug"] // Doug Jacobsen has 4 received payments associated with his Jobs PCQB_RqExecute [Select; Results:$result] // Value of $result is 0 PCQB_SGetXML [Select; Results:$responseXML; XML Document Type:"Response"] // Contained the resulting XML set describing 4 received payments If you wanted to use the date range instead of a customer reference (for example, all received payments in January, 2021, since the sample file is in the future), you could structure your script like so: PCQB_RqNew [Select; Results:$result; Request Type:"ReceivePaymentQuery"] PCQB_RqAddFieldWithValue [Select; Results:$result; QB Field Name:"TxnDateRangeFilter::FromTxnDate"; Field Value:"01/01/2021"] // Start from January 1st, 2021 PCQB_RqAddFieldWithValue [Select; Results:$result; QB Field Name:"TxnDateRangeFilter::ToTxnDate"; Field Value:"01/31/2021"] // End on January 31st, 2021 PCQB_RqExecute [Select; Results:$result] // Value of $result is 0 PCQB_SGetXML [Select; Results:$responseXML; XML Document Type:"Response"] // Contained the resulting XML set describing 6 received payments within the month of January 2021 Hope this helps! - Chris
  2. Handling Receive Payment Transactions

    Thank you for catching those typos, Geoffrey! Post has been updated to reflect those changes.
  3. How to Push a Job

    Pushing a job is identical to pushing a Customer with one exception. You need to add the ParentRef to the request. The "ParentRef::ListID” or "ParentRef::FullName” should be included in the request to add. The request will now be a job instead of a top level customer. In the example above the ListID and FullName refer be the ListID and FullName of the parent or top level customer in QBs. You will need to obtain the existing customer List ID or customer full name from QBs. For further details on ListID and FullName fields, please reference the OSR.
  4. You can query a customer in QuickBooks based on the customer name and obtain the LIST ID by doing the following: PCQB_RqNew ( "CustomerQuery" ) PCQB_RqAddFieldWithValue( "FullName" ; CNTCT::FullName ) The ListID is returned in the response. PCQB_RsOpenFirstRecord PCQB_RsGetFirstFieldValue( "ListID" ) For a detailed list of all available or required fields in a CustomerQuery, please reference the OSR at: https://developer-static.intuit.com/qbSDK-current/Common/newOSR/index.html. You may also want to refer to the Developer's Guide for navigational tips on how to properly use the OSR.
  5. # # This script snippet demonstrates applying a received payment to multiple invoices. # It assumes that the FileMaker solution has a 'join' table between the payment and the invoice(s), and from the # join table the txn id of the invoice is accessible. # PCQB_RqNew( "ReceivePaymentAdd" ) #adding the remainder of the fields left out of this sample in the interest of brevity #ensure to add them in your script. # #now apply this payment to the invoices.. #go to the related records that indicate which invoices the current FM payment is applied to #from these records it will be necessary to have access to the invoice txn id and the amount applied to the invoice - design your fm schema accordingly # Go to Related Record..... Go to Record/Request/Page[ First ] #create the 'related records' to the request Loop # use pcqb_rqaddrelatedrecord to add an application of the payment to a transaction/invoice PCQB_RqAddRelatedRecord( "AppliedToTxnAdd" ) # # now add the transaction id for the invoice - this tells QB that this is the invoice to which we are applying part of the payment PCQB_RqAddFieldWithValue( "TxnId" ; INV_PMT::Invoice_TXNID ) #note that INV_PMT::Invoice_TXNID is a place holder for your table/field holding the txnid for the invoice # # now add the payment amount - the part of the payment applied to the invoice PCQB_RqAddFieldWithValue( "PaymentAmount" : INV_PMT::Applied_Amount ) #note that INV_PMT::Applied_Amount is a place holder for your table/field holding the amount of the current payment that is applied to the invoice # #very important! - close the related record in the request PCQB_RqCloseRelatedRecord # #and navigate to the next invoice to which the payment is to be applied Go to Record/Request/Page[ Next ; Exit After Last ] End Loop # #
  6. QuickBooks receive payment transactions can be added, queried, and deleted. This section describes the effects of sending a ReceivePaymentAdd request object to QuickBooks. Applying a Payment: In a ReceivePaymentAdd object, TotalAmount is optional. TotalAmount represents the total amount of money that is being received from the customer named in the CustomerRef. The reason TotalAmount is not required is that a ReceivePaymentAdd object can be used to set credits or discounts without receiving any payment. You can use either AppliedToTxnAdd or IsAutoApply to distribute the received payment, as described in the following sections. Distributing the Payment Explicitly: You can include one or more instances of AppliedToTxnAdd, which allows you to specify exactly how to distribute TotalAmount for this customer job. Each instance of AppliedToTxnAdd refers to a different transaction, assigning a PaymentAmount to each one. (If you include AppliedToTxnAdd aggregates with duplicate TxnIDs, you will receive a status code error.) You need to know the transaction ID of each transaction to which payment is applied. In QuickBooks, the main type of transactions that can receive payment are as follows: • Invoices • General journal debits • Checks (for example, a customer job might receive a payment reimbursing a check that was written for an expense for that customer job) • Statement charges Table 18-1 attached shows how the sum of the payment amounts relates to the TotalAmount specified. The sum of the PaymentAmount elements in all the AppliedToTxnAdd aggregates should be less than or equal to the TotalAmount (in the ReceivePaymentAdd object). Applying the Payment “Automatically”: The IsAutoApply flag is used instead of AppliedToTxnAdd. This flag allows QuickBooks to apply the payment according to its set of rules, or simply to receive the payment without applying it to a specific transaction, as follows: • If IsAutoApply is true, QuickBooks applies TotalAmount according to the following rules: > If it finds an outstanding transaction for this customer job that exactly matches TotalAmount, it applies the payment to that transaction. > If no exact match is found, the payment is applied to the outstanding transactions beginning with the oldest one. Within the QuickBooks user interface, you can set credits or discounts even when you auto-apply a payment, but you cannot do this through the SDK. • If IsAutoApply is false, QuickBooks receives the payment but does not apply it to any outstanding transaction. QuickBooks creates a credit that will appear on the customer job’s next transaction (not on the current transaction). For example, the ReceivePaymentAdd request shown in Listing 18-1 will result in a credit of $620.40 being available to the Smith:kitchen customer job account. On the next transaction involving the Smith:kitchen customer job, at least $620.40 of credit will be available. (More than $620.40 will be available if this customer job already had a credit.) Listing 18-1 ReceivePaymentAdd request with IsAutoApply set to false; creating a credit: PCQB_RqNew( “ReceivePaymentAdd” ) PCQB_RqAddFieldWithValue( “CustomerRef::FullName” ; “Smith:kitchen” ) PCQB_RqAddFieldWithValue( “ARAccountRef::FullName” ; “Accounts Receivable” ) PCQB_RqAddFieldWithValue( “TotalAmount” ; “620.40” ) PCQB_RqAddFieldWithValue( “IsAutoApply” ; “false” ) Setting Discounts: Applying a discount reduces the amount that is to be received from the customer job. The discount is debited from the account referenced by DiscountAccountRef. In the QuickBooks user interface you can also apply discounts to statement charges, but you cannot do this through the SDK. You can apply a discount to an invoice transaction by including a DiscountAmount in an AppliedToTxnAdd aggregate. You cannot set a discount if you auto-apply the payment. Setting Credits: You can set a credit (add credit to a customer job account) by including the SetCredit aggregate in an AppliedToTxnAdd aggregate. You cannot set a credit if you auto-apply the payment. If you set one or more credits in a ReceivePaymentAdd request but do not distribute a payment or set a discount, then no transaction will be created. Setting a credit merely creates links between existing transactions (for example, between a credit memo transaction and an invoice transaction), and no information about these links will be returned to you in the ReceivePaymentRet response. The AppliedToTxnRet aggregate included in the returned ReceivePaymentRet object will not refer directly to any credit that was set. If you want information about credits, you must do a query on the TxnID returned by AppliedToTxnRet. For example, if AppliedToTxnRet refers to an invoice with a particular TxnID, if you query that TxnID you can get information about credit memos that are linked to that transaction. For more information and an example of setting a credit, see “Example: Creating Links Only.” Example: Creating Links Only Listing 18-2 shows a ReceivePaymentAdd object that sets a credit but does not include a PaymentAmount or DiscountAmount element. This ReceivePaymentAdd object will create a link between a credit memo and an invoice transaction, but will not create a new transaction. The customer named Smith previously returned merchandise, and a credit memo was created for their account. A CreditMemoQueryRq query returned information about the amount and transaction ID of this credit memo (110.29 and 120-1012533559). In Listing 18-2, the full amount from the credit memo is applied to the customer job Smith:kitchen, and a link is created to the invoice with the TxnID of 24-974954. The balance of that invoice will be reduced by $110.29, and closed altogether if the previous balance was $110.29. Listing 18-2 ReceivePaymentAdd object that creates links but does not create a transaction: PCQB_RqNew( “ReceivePaymentAdd” ) PCQB_RqAddFieldWithValue( “CustomerRef::FullName” ; “Smith:kitchen” ) PCQB_RqAddRelatedRecord( “AppliedToTxnAdd” ) PCQB_RqAddFieldWithValue( “TxnID” ; “24-974954” ) PCQB_RqAddRealtedRecord( “SetCredit” ) PCQB_RqAddFieldWithValue( “CreditTxnID” ; “120-1012533559” ) PCQB_RqAddFieldWithValue( “AppliedAmount” ; “110.29” ) PCQB_RqCloseRelatedRecord //closes the SetCredit record PCQB_RqCloseRelatedRecord //closes the AppliedToTxnAdd record A ReceivePaymentAdd object that does not create a transaction will return a lean AppliedToTxnRet aggregate this page. For example, Listing 18-3 shows a ReceivePaymentRet object that could be returned from the ReceivePaymentAdd request shown in Listing 18-2. Listing 18-3 ReceivePaymentRet object returned by the ReceivePaymentAddRq shown in Listing 18-2: <ReceivePaymentAddRs> requestID="356089" statusCode="0" statusSeverity="Info" statusMessage="Status OK"> <ReceivePaymentRet> <AppliedToTxnRet> <TxnID>24-974954</TxnID> <TxnType>Invoice</TxnType> <TxnDate>2002-02-10</TxnDate> </AppliedToTxnRet> </ReceivePaymentRet> </ReceivePaymentAddRs> How to parse the object... PCQB_RsOpenFirstRecord PCQB_RsOpenFirstRelatedRecord( “AppliedToTxnRet” ) PCQB_RsGerFirstFieldValue( “TxnID” ) //The transaction id for the related transaction PCQB_RsGetFirstFieldValue( “TxnType” ) //The type for the related transaction PCQB_RsGetFirstFieldValue( “TxnDate” ) //the date for the related transaction Getting a small response such as this might prompt you to query the specified invoice further to learn about any linked transactions. For example, after receiving the response shown in Listing 18-3, you might send an InvoiceQueryRq with TxnID of 24-974954 and IncludeLinkedTxns set to true. The query would return a LinkedTxn aggregate representing a credit memo with TxnID of 120-1012533559. For more information, see “Linked Transactions,”. You can perform additional queries for links only if the affected transaction (the transaction returned in the AppliedToTxnRet) is an invoice. For example, if the TxnID 24-974954 had a TxnType of JournalEntry, it would not be possible to query the journal entry to find out about linked transactions because a JournalEntryQueryRq does not include an IncludeLinkedTxns flag. Example: Applying Payment, Credit, and Discount in One Request Listing 18-4 shows a request that applies a payment, credit, and discount. The invoice with TxnID 43-222560 has a balance of $100.00, and a payment is received for $100.00. The invoice will be closed, but there will also be an unused payment, because both a credit (for $5.00) and a discount (for $7.00) are set. QuickBooks will reduce the internal payment amount to $88.00 [$100.00 - ($5.00 + $7.00)]. This example will produce an overpayment of $12.00, so UnusedPayment will be 12.00 in the returned ReceivePaymentRet object. Listing 18-4 Applying Payment, Credit, and Discount in a ReceivePaymentAdd Request: PCQB_RqNew( “ReceivePaymentAdd” ) ... PCQB_RqAddFieldWithValue( “TotalAmount” ; “100.00” ) PCQB_RqAddRelatedRecord( “AppliedToTxnAdd” ) PCQB_RqAddFieldWithValue( “TxnID” ; “43-222560” ) PCQB_RqAddFieldWithValue( “PaymentAmount” ; “100.00” ) PCQB_RqAddRelatedRecord( “SetCredit” ) PCQB_RqAddFieldWithValue( “CreditTxnID” ; “4552-22629” ) PCQB_RqAddFieldWithValue( “AppliedAmount” ; “5.00” ) PCQB_RqCloseRelatedRecord //closes the SetCredit record PCQB_RqAddFieldWithValue( “DiscountAmount” ; “7.00” ) PCQB_RqAddFieldWithValue( “DiscountAccountRef::FullName” ; “discount” ) PCQB_RqCloseRelatedRecord //closes the AppliedToTxnAdd record

    Hi Wendy, It looks like the call to PCQO_RqUseJSON is not storing a result in the "Results" specifier. It's possible that PCQO_RqUseJSON might be experiencing an error (such as a malformed JSON document or some other exception), which would prevent the plug-in from properly replacing the request JSON with the contents of $json.payitem; that's why the second PCQO_RqExecute is still executing the vendor query JSON from before. If you can, could you store the results of PCQO_RqUseJSON into a variable (the $result variable should work just fine), and check it to see if the result is "!!ERROR!!" or "?"? If so, PCQO_SGetStatus should help tell a little more about what could be the root of the issue. Hope this helps!
  8. No of contacts not matched

    Just a quick follow-up regarding this: Apple Contacts has an automatic contact linking feature that will link contact records that come from multiple sources (such as Exchange, Facebook, iCloud, etc.) into a single contact card. That way, if there are, for instance, 3 contact records for "John Smith" with the similar information, Apple Contacts will condense the three records into one, and reference the sources in the "Links" section of the contact card. The Address Book Manipulator plug-in does not read condensed/linked contact records when accessing them in memory, and will pull three separate contact cards for "John Smith" in the example above. As a note, the data for each contact record is maintained after being linked; there is no lost information. To reconcile which contacts are linked, a developer may perform a find in FileMaker after pulling contacts and compare those duplicate records with matching records in Apple Contacts. Hopefully that helps! - PCIPal
  9. No of contacts not matched

    Hi jameshoty, Someone from our team has responded to your support ticket via email with more information. - PCIPal
  10. With the holidays right around the corner, Devon 2017 feels like a long time ago. If you are missing that exciting buzz experienced at DevCon, we invite you to take a listen to FileMaker Talk’s podcast from DevCon – “ Live at DevCon in Phoenix 2017” . You need to open it up in iTunes, but it will certainly transport you right back to Phoenix (lazy river and 99-degree weather not included). The podcast starts out with Matt Navarre interviewing Jesse Barnum from 360Works. Jesse talks until about minute 11:40 and discusses their MirrorSync product, including its pricing and what’s new with version 4. Jesse’s portion of the podcast also includes an insightful discussion on 360Deploy and how that product works. After Jesse, our very own CEO, Marc Larochelle, is on from about minute 11:40 until 41:00. Marc talks about what’s new (as of July 2017) here at Productive Computing – which included discussing our latest plug-in, the Exchange Manipulator SE, and its functionality. Marc also hinted that a Google plug-in might be in the pipeline for PCI (wink) and he mentioned that we are now Intuit Authorized QuickBooks Resellers! Marc and Matt also discussed AWS (Amazon Web Services) and PCI’s hosting services, including how we manage our servers and why we use Amazon Workspaces. Lastly, they discussed PCI’s hiring and training practices (including our training program for all new hires). At minute 41:41, Nicholas Orr from Goyacomes on to talk about their flagship product, BaseElements (which now has a new annual pricing model, making it more affordable and easier to upgrade) and RESTfm (cool story – FileMaker came to Goya to discuss RESTfm when they were creating the FileMaker Data API). Nick also discusses his vendor session, which touched on the differences between RESTfm and Data API, including format flexibility and authentication flexibility. The fourth and fifth guests on the show are James (Dave) Ramsey and Todd Geist from Geist Interactive at minute 52:15. In his segment, Todd’s talks about his 2017 FileMaker Award (for Advocacy) and Dave discusses their new product – FMPerception – and what exactly it is/does (hint: FileMaker DDR analysis tool that is crazy quick). Todd also talks about his training day session and what topics that training covered. The last guest on the show is Mark Richman from Skeleton Key at 1 hour and 4 minutes. Mark discusses Skeleton Key’s extensive participation in DevCon, including the many sessions he and his staff presented during the week (Security 101 and The ABCs of reselling; 7 Tips for Getting More out of FileMaker Cloud and Introduction to SQL and ODBC; The Power of Bi-Directional Relationships and Programming for Power Users). Mark also gave his opinions on the benefits of being a one-stop shop for your clients and the benefits of reselling FileMaker software. There are some great interviews here – hope you enjoy! View the full article
  11. Check Connection Mid-script

    Hi Wendy, Could you please let me know which version of the plug-in you are currently using? You can find out by using the demo; it should be listed in the "Plug-in Version" field. Please note that if you are using the 64-bit version of FileMaker with the 64-bit version of FM Books Connector v9, there was a bug in early versions of FM Books Connector before the release of v9.0.1.1 where the 64-bit version of the QB Bridge would lose its session after 2 minutes of inactivity or during a large volume of requests. This fix will require a reinstallation of the latest version of FM Books Connector v9. I hope this helps!
  12. Richard Carlton (Richard Carlton Consulting) recently did a video with our CEO, Marc, and our plug-in developer, Chris, discussing our sleeper plug-in, the Biometric Fingerprint Reader. Released in 2011, this plug-in connects your FileMaker solution to the U.are.U fingerprint reader, enabling your solution to scan fingerprints for fast identification and secure verification. We don’t talk about this plug-in very much nor do we spend a lot of time marketing it, but it’s a well-designed, tried and true, a workhorse of a plug-in. If you are curious to learn more, check out the video below. In this 15 minute video they cover: 1. What is the Biometric Fingerprint Reader 2. How the plug-in works 3. Why companies need and use the plug-in (integration example) 4. What the plug-in is and what it is not 5. Demo of the plug-in 6. Discussion of practical application 7. This is Windows only plug-in – is there the possibility of a Mac version? View the full article
  13. When it comes to hosting your FileMaker solution, there are a lot of options out there. You can host it yourself onsite, you can host with a service, or you can explore FileMaker Cloud. Let’s assume that you’ve decided the hassle and costs associated with hosting your solution yourself are too prohibitive and you’ve decided to host with a service. Now you’re looking at plans. There is shared hosting and dedicated hosting and concierge services for FileMaker Cloud (not discussed in this blog, but follow this link for more info). Shared Hosting Shared hosting is the most economical option available on the market and very appealing to a lot of people looking to host their FileMaker solution. In order to figure out if shared hosting is the right option for you and to help you choose between our Starter or Professional Plan, let’s start with a few questions: First: What version of FileMaker Pro is your solution currently running on? What version of FileMaker Server are you currently using and what version of FileMaker Pro and FileMaker Server do you want or need to be on? Okay, that was technically three questions, but they are all important. Our shared hosting plans support FileMaker Server 11-14 and FileMaker Pro (client) 7-16. The compatibility chart below details what FileMaker Pro versions are available on the different FileMaker Server versions. If don’t want to or don’t need to upgrade to FileMaker Server 15 or above, a shared hosting plan could be perfect for your needs. Second: How many files do you want to host (and how big are your files)? The Starter plan is ideal for one file and up to 1 GB of data. If you need to host more than one file, the Professional plan supports up to five database files and 5 GBs of storage. Third: Do you need FileMaker WebDirect or FileMaker Go connections? If yes, you need to go with the Professional plan. Our Starter plan does not support WebDirect or Go connections. Dedicated Hosting If you want or need to be on FileMaker Server 15 or higher, you need to go with dedicated hosting. We offer four plans (Micro Team, Small Team, Medium Team, and Large Team – henceforth referred to as Micro, Small, Medium, and Large) designed to cover, accommodate, and service a wide variety of needs and requirements. Let’s review some of the factors that go into deciding which plan is the best fit for you. 1. File size Each plan allows you to upload up to 125 database files, but the size of your files is a determining factor in deciding which plan is right for you. Our dedicated hosting plans offer varying quantities of disk space to accommodate the overall size of your files. Our Micro and Small plans have limited storage. If the files being hosted are too large, it becomes difficult to provide redundant backups without incurring additional costs. If your files’ total sizes are less than 5 GB, you are probably okay going with the Micro plan. With 60 GB of disk space available, anything larger than 5 GB becomes too big for the standard backup routines that are included with the plan. What if your FileMaker files are just a little too big for the Micro plan? Then the Small plan should work for you since it can host files up to 10 GB. With either of these plans, you can also purchase additional blocks of 100 GB for $20 a month. If you have files over 10 GB, then you may want to consider a Medium or Large plan. These servers can hold files up to 150 GB – giving you lots of room for your FileMaker file and even external data too. 2. Performance What kind of performance do you need and what do you intend to do on your server? If you plan to run continuous routines or regular audit systems, you are going to want to opt for the Medium or Large plan. With more RAM available, these plans are better equipped to handle complex processes that won’t result in lag. Interested in learning more about FileMaker performance when hosting? Check out this video Marc Larochelle, our CEO, did: Click here to view the embedded video. 3. Bandwidth Depending upon how you use your solution, you may need a lot of bandwidth. Several things can determine if you need unlimited bandwidth: A. if you work with a lot of interactive containers B. if you plan to regularly download data to your local machine C. if you use custom web publishing D. your backup is going to Dropbox All of these use a lot of bandwidth, so we’d suggest our Medium or Large plan. If you use your solution more for regular data entry and as storage for historical documents that you are not downloading daily – you’ll be fine with a Small plan (or maybe even a Micro). 4. Number of FileMaker users / WebDirect access Here are two more things to consider. Do you have less than 10 FileMaker Pro users? Look at the Micro Plan. Anything over 10 users, your options are wide open with the Small, Medium or Large plans. While all plans support FileMaker Go access, only the Small, Medium, and Large Team plans support FileMaker WebDirect access. If you intend to have more than 10 users connecting to your solution via FileMaker Go or you want to use WebDirect, also stay with any plan above the Micro plan. The Small, Medium and Large plans come with 8 GB or 16 GB of RAM, respectively – which is needed if you intend to have a larger number of users connecting remotely. 5. Backups Each of our dedicated plans have a robust backup schedule. Your ideal plan will depend on your backup needs. The Micro and Small plans keep a daily backup for 7 days. At any point, your oldest backup will be from one week ago. Additional backups or DropBox storage (for archive purposes) may be requested for an added cost. If you need more longevity on your backups, you can consider a Medium or Large plan. These plans hold backups for up to one year. Both plans (Medium and Large) include twice daily backups completed at 12:30 pm and 1:00 am. These daily backups are kept for one (1) week. We then run weekly backups that are kept for one (1) month and monthly backups that are kept for up to one (1) year. For redundancy and disaster recovery, all backups are stored on a 1 TB external drive and a daily backup is uploaded to a dedicated folder on Dropbox (see #6). If you are considering creating your own backup schedules, we highly recommend the Medium or Large plan. Additional backups can be costly on the Micro or Small plan, due to the fact both are running on AWS. AWS charges per GB of space, as well as bandwidth usage. 6. Dropbox Do you want your backups available via Dropbox and do you want the ability to access a Dropbox backup up to 365 days later? Dropbox is automatically included with Medium and Large plans. Dropbox is available with our Micro and Small plans, but it does cost extra. With Dropbox, we can provide you with backups that are up to 365 days old. Dropbox also allows for more redundant storage of your backups. 7. SSL Certificates We include a wildcard SSL certificate with all of our plans. If you would like a customized SSL cert for a custom domain name or other requirements, this options is available for an additional fee. One last piece of advice. Before contacting a hosting provider, you should know: 1. How many users you will have using FileMaker Pro, Go, and WebDirect. 2. How many files you want to host, as well as the size of those files. 3. What version of FileMaker Pro and Server you plan to use. If you’re interested in hosting your solution with us, give us a call today (760-510-1200) and talk to one of our hosting engineers. We’ll discuss your requirements and specifications and get you on track with exactly what you need. View the full article
  14. If you receive this error when using PDF Manipulator DC, you will need to install the Acrobat plug-in. Please follow these steps: 1) Close Acrobat and FileMaker 2) In Finder, navigate to Go > Go To Folder... and type in "~Library/Application Support/Adobe/Acrobat/DC/Plug-ins 3) Copy and Paste the Acrobat plug-in “PDFManipulatorDCAcrobatPlugin.acroplugin” (which can be found in the “Extras” folder in the Installer) into the Plug-ins folder If you're using an older version of the PDF Manipulator: 1) Close Acrobat and FileMaker 2) Navigate to Applications > Adobe Acrobat DC, right click on Adobe Acrobat and select “Show Package Contents” 3) A new Window will pop up. Navigate to Contents > Plug-ins 4) Copy and Paste the Acrobat plug-in “PDFManipulatorDCAcrobatPlugin.acroplugin” (which can be found in the “Extras” folder in the Installer) into the Contents > Plug-ins folder from step 3 above
  15. FM Credit Card v1 was first released in April of 2011 and discontinued in August of 2015. After increased interest from clients, we decided to bring the plug-in back to life, bigger and better than ever, and released v2 in September of 2017. If you are a v1 client, you might be wondering, what’s so great about v2? Well, this blog will answer that for you. Here are seven good reasons to upgrade to FM Credit Card version 2. Don’t feel like reading? Check out this quick video from our CEO, Marc, discussing the plug-in and v2 enhancements: Click here to view the embedded video. 1) FileMaker 16 Compatible. FM Credit Card v2 is compatible with FileMaker 14 -16. V1 is compatible with FileMaker 13 (which FileMaker has deprecated support for). Make your solution modern and take advantage of all that FileMaker 16 has to offer. 2) FileMaker 16 Script Steps. With the release of FileMaker 16, we added FileMaker 16 script step functionality to all of our plug-ins. Take advantage of this modern scripting method with version 2. Want to learn more about FileMaker 16 script steps? Here is a video of our CEO, Marc, explaining what they are: Click here to view the embedded video. 3) Gateway Compatibility. FM Credit Card is now compatible with Authorize.net and Authorize.net emulator gateways, as well as PayPal. And, with version 2, we consolidated all of the gateway-specific plug-in functions to more general functions to make it easier to program your scripts. Our plug-in developer also organized the functions to provide more flexibility and future expandability with the function calls to the plug-in. 4) Security Compliance. Version 2 is compliant with the latest security requirements and industry standards of TLS 1.2. These strict security requirements are mandatory for any modern payment transaction. 5) Card-present transactions. With version 2, if the card is present, you can conveniently swipe it right into FileMaker with a keyboard-emulating card reader – no need to type in the card info. 6) Server-side compatibility. This means you can now integrate with FileMaker Go, FileMaker WebDirect and Custom Web Publishing by way of the “perform script on server” script step. This enhancement greatly expands your deployment options and allows you to construct the exact workflow your company needs – be it on desktop, iOS device, or the web. 7) Free updates. Because FM Credit Card is a SaaS product, we will always ensure it is compatible with the three ever-changing environmental variables including: both the Windows and Mac operating systems, the payment gateways themselves (i.e. Authorize.net), and the latest version of FileMaker, which we all know changes yearly. In any and all of these cases, we have you covered. Not only does SaaS cover future compatibility, it includes access to any new features we may build into the plug-in over time. Starting at $35/year for a single user license, there is no reason not to upgrade! Visit www.fm-creditcard.com today to download the latest plug-in and take it for a test drive in our updated demo. View the full article

Important Information

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