RyanFarrington
Qrew Member
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Quickbooks invoice pipeline issue
Hi Jessica, Perhaps check that the field type for [Amount] that you're mapping to the QuickBooks 'amount' field is a numerical field and not a text representation of a number. ------------------------------ Ryan Farrington Graphic designer, project manager, copywriter, engraver, internal Quick Base developer rfarrington@experiencepinpoint.com ------------------------------40Views0likes0CommentsRe: Correct format for Address in Pipelines, if field name has a space
Thank you for posting this! I was just working on a pipeline with address fields and was about to report this bug. ------------------------------ Ryan Farrington Graphic designer, project manager, copywriter, engraver, internal Quick Base developer rfarrington@experiencepinpoint.com ------------------------------31Views0likes1CommentRe: Introducing Unlimited Quickbase Channel Usage in Pipelines
Are the "purple channels" also free now? Bucket, CSV Handler, Callable pipelines, Clock, JSON Handler, Text, and Webhooks? I'd like to use some pipelines that apply a number of regular expressions, but it would very quickly eat up our step runs. (These are in the Text channel.)41Views0likes0CommentsCustom Save button, API calls, and redirects to specific pages
(This is kind of continued from this thread, but the question/subject is different) What I would like to happen Click a button on a Contact record, Form 1 Takes you to Contact record, Form 2 Enter information on Form 2. Click button Saves the Contact record, API_AddRecord Creates a new Client with the just-saved info from the Contact record API_GenAddRecordForm starts a new Project related to the Contact and (ideally) the new Client. Issue I don't know how to get #3 to work. I've tried different methods. Problems Either the client record isn't created with the updated info from step 2 Or the system goes to an XML result page instead of redirecting to 3c First: the client record isn't created with the updated info from step 2 Acheived with a button on Form 1. The button's code outline is like this: API_EditRecord to automatically change certain data about the contact rdr= to the contact on Form 2 &NextURL= to specify what should happen when Form 2 is saved API_AddRecord to automatically create the new Client record rdr= API_GenAddRecordForm to create a new Project Second: the system goes to an XML result page instead of redirecting to 3c Achieved by a custom button on Form 2 with a javascript LinkAway. The button's code outline: href='javascript:LinkAway(\"... to save the updated data in the record API_AddRecord to automatically create the new Client record rdr= API_GenAddRecordForm to create a new Project It doesn't like anything after step 1.a. and returns the XML result page. I'm pretty sure it successfully creates the client, but refuses to go on to the Project. I've also tried having it just &disprec=1 instead of redirect to the new project but even that doesn't work. I'd be fine with even redirecting to the Contact record, Form 3, so the user just has to click an "Add Project" button, but redirecting there doesn't work either If anyone has any ideas how to achieve this multi-step process, I'd appreciate the help! ------------------------------ Ryan Farrington Graphic designer, project manager, copywriter, engraver, internal Quick Base developer rfarrington@experiencepinpoint.com ------------------------------20Views0likes1CommentRe: Trying to auto-populate a field statically
It sounds like what you need is a lookup of the [Customer Name-Opportunity Record Number] field. Go to your Table-to-Table Relationships, find the one that relates to Quotes, then click "Add Lookup Fields" button. With the method you described, however, If you create an additional quote from that opportunity, it will have the same Customer Name-Opportunity Record Number ------------------------------ Ryan Farrington Graphic designer, project manager, copywriter, engraver, internal Quick Base developer rfarrington@experiencepinpoint.com ------------------------------16Views0likes2CommentsRe: Is there a limit to number of fields you can specify in a GET-method API_AddRecord?
I tested it with another record and got the same failure. Doesn't seem to be data-dependent. ------------------------------ Ryan Farrington Graphic designer, project manager, copywriter, engraver, internal Quick Base developer rfarrington@experiencepinpoint.com ------------------------------3Views0likes1CommentRe: Is there a limit to number of fields you can specify in a GET-method API_AddRecord?
I've done more testing and found that the system prefers certain fields toward the beginning of the URL, otherwise it won't write the values to the fields in the new record. I have no idea why! (I'm going to try working in the [Billing Address] field after I make more progress. I haven't gotten that to work yet.) With the "preferred" fields listed first, I tested the button and appended &disprec=1 so it would land on the newly created record. That only worked when I put &disprec=1 early in the URL. With that working, I thought I would try just URLTWO, which is an API_GenAddRecordForm. That worked. Now it's a matter of getting it to create the first record and then redirect to URLTWO, which it refuses to do. //URLONE URLRoot() & "db/" & [_DBID_CLIENTS] & "?a=API_AddRecord&apptoken=XXXXXXXX" & "&_fid_37=" & URLEncode([Website]) & "&_fid_43=" & URLEncode(User()) //Account Lead & "&_fid_173=" & URLEncode([Record ID#]) //Trigger Contact & "&_fid_6=" & URLEncode([Company Name]) //required field & "&_fid_89=" & URLEncode([Related Payment Term]) //required field & "&_fid_99=" & URLEncode([Related Tax Code]) //required field & "&_fid_62=" & URLEncode([Lead Source]) & "&_fid_126=" & URLEncode(User()) //Won By & "&_fid_83=" & URLEncode(User()) //Project Manager & "&_fid_33=Prospect" & "&_fid_38=" & URLEncode([Industry]) & "&rdr=" & URLEncode( //URLTWO URLRoot() & "db/" & [_DBID_QUOTES] & "?a=API_GenAddRecordForm" & "&_fid_244=" & URLEncode(Today()+Days(7)) & "&_fid_214=" & URLEncode([Record ID#]) //Related Contact & "&_fid_653=" & URLEncode([Record ID#]) //Trigger Contact ) ------------------------------ Ryan Farrington Graphic designer, project manager, copywriter, engraver, internal Quick Base developer rfarrington@experiencepinpoint.com ------------------------------0Views0likes0CommentsRe: Is there a limit to number of fields you can specify in a GET-method API_AddRecord?
Hi Mark, as you suggested, I added URLEncode to questionable fields. But it still doesn't write anything beyond the 7th field. The linkaway is to get the form to save before continuing, and that works fine. ------------------------------ Ryan Farrington Graphic designer, project manager, copywriter, engraver, internal Quick Base developer rfarrington@experiencepinpoint.com ------------------------------2Views0likes5CommentsRe: Is there a limit to number of fields you can specify in a GET-method API_AddRecord?
Below is the code. I used to have field 89, a required field, in spot number 8, and no matter what I put in field 89 I got error 50, saying that required field 89 was blank. I moved it to the beginning of the list and now the record gets created. But the Billing Address doesn't get populated in the new client record. Quick Base also just returns me to the XML output page instead of redirecting. var text URLONE = // create the client URLRoot() & "db/" & [_DBID_CLIENTS] & "?a=API_AddRecord&apptoken=XXXXXXXXXXXXXXXXXXXXXXXXX" & "&_fid_89=" & [Related Payment Term] & "&_fid_99=" & [Tax Code] & "&_fid_6=" & [Company Name] & "&_fid_62=" & [Lead Source] & "&_fid_126=" & UserToEmail(User()) & "&_fid_33=Prospect" & "&_fid_38=" & URLEncode([Industry]) & "&_fid_37=" & [Website] & "&_fid_43=" & UserToEmail(User()) //Account Lead & "&_fid_83=" & UserToEmail(User()) //Project Manager & "&_fid_18=" & [Billing Address] & "&_fid_25=" & [Billing Address] & "&_fid_173=" & [Record ID#] ; var text URLTWO = ... "<a href='javascript:LinkAway(\"" & $URLONE & "&rdr=" & URLEncode($URLTWO) & "\");'>Confirm info & add opportunity</a>" ------------------------------ Ryan Farrington Graphic designer, project manager, copywriter, engraver, internal Quick Base developer rfarrington@experiencepinpoint.com ------------------------------1View0likes7CommentsIs there a limit to number of fields you can specify in a GET-method API_AddRecord?
I'm making a button that creates a new record using the GET method. I'm using API_AddRecord. I want to specify the values for 13 fields, but it seems the operation stops after 7 fields. It creates the record, but without the 6 remaining fields filled out, and it doesn't go on to the proper redirect I specify. This makes me suspect there is a limit to the number of fields you can specify in in a GET API_AddRecord operation. Questions: 1) is this true--on purpose? 2) is this true--as a bug? 3) can I use a different method to specify more fields and give me the redirect I want? ------------------------------ Ryan Farrington Graphic designer, project manager, copywriter, engraver, internal Quick Base developer rfarrington@experiencepinpoint.com ------------------------------5Views0likes9Comments