Expand all | Collapse all

Webmerge URL & Bad Sign-In Ticket

  • 1.  Webmerge URL & Bad Sign-In Ticket

    Posted 05-29-2018 23:41
    I am trying to use Quick Base -> Zapier -> Webmerge for generating quote/invoice documents. I've gotten as far as merging data, but the URL I'm sending will not show API_GenResultsTable I need. It should be populated with a table of child records relative to parent record. This is the rendering when merged as PDF:

    The merge field in Webmerge template is:
    {smarty_curl($report_url) nofilter}

    The $report_url variable is populated via Zapier with data originating from Quick Base. My Quick Base-originated URL is the following:

    URLRoot() & "db/" & [Child Table Dbid]
    & "?a=API_GenResultsTable&query={'219'.XEX.'1'}AND{'111'.EX.'" & [Record ID#] & "'}AND&clist=351.399.48.47.45&_fid_111=" & URLEncode([Case Number]) & "&usertoken=" & [webhook-usertoken] &
    "&apptoken=" & [AppToken - Zapier]

    The strange thing is it works for another Quick Base app that I'm using. I've been stuck on trying to pick apart the differences in how I set it up and I can't figure it out.

    I haven't had a lot of luck with the Quick Base forums so hopefully someone can help out this time.


  • 2.  RE: Webmerge URL & Bad Sign-In Ticket

    Posted 05-30-2018 18:29
    It was an error on Webmerge side. Duplicated the working document and replaced HTML, then it worked.