BrianRichardso1
Qrew Trainee
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: RESTful API Header
Does it return the token to you in the response Header or in the body? If it's in the body then you could potentially iterate over the JSON objects using the JSON channel, then you'll get the value back as a field you can then use in the subsequent JSON request Header field. ie if you iterate over the objects in step C and get a field called "token" you could then put something like this in JSON Request Header field (example here is if the auth header name is "Authorization") : "AUTHORIZATION: {{c.token}}" If that doesn't work you could maybe iterate the JSON objects and store the values in a Quickbase table somewhere using the Add or Update Record Quickbase channel, then lookup the value in a later step or separate pipeline step and include it using the same format above. If you're getting the token back in the header then I'd be interested if anyone on this community knows how to capture header data and use it in subsequent pipeline steps. The JSON Request step only provides a "Header Name" and "Header Value" field without an obvious way to differentiate amongst all the returned headers. I tried storing the headers in a Quickbase table but it won't store them. Sorry for the tome... hopefully something works for you... I'm just getting my API legs under me with Pipelines too. ------------------------------ Brian Richardson ------------------------------Re: Form Field Display
Not sure... I haven't done a formula as a proxy. It appears from the help text that you have to ensure your formula utilizes a lookup field as part of the formula, for it to be available. Perhaps that's the issue? Beyond that I can't say, sorry. ------Original Message------ Brian: Thank you. I am referencing proxy fields. The proxy fields are Formula-txt fields. Could that be the issue? ------------------------------ Dirk Ruana ------------------------------Re: Form Field Display
Hey Dirk, you need a proxy field setup for each of those relationships. Proxies display a value or words instead of the Record ID. Setup a lookup field and then in the Properties of the Reference field (likely something like Related xxx) select that lookup in the Proxy Field dropdown. More info here: https://help.quickbase.com/user-assistance/ref_proxy.html -- Brian Richardson Tools and Resource Manager Enterprise Project Management Office Mobile Mountaineer The information contained in this email message and its attachments is intended only for the private and confidential use of the recipient(s) named above, unless the sender expressly agrees otherwise. Transmission of email over the Internet is not a secure communications medium. If you are requesting or have requested the transmittal of personal data, as defined in applicable privacy laws by means of email or in an attachment to email, you must select a more secure alternate means of transmittal that supports your obligations to protect such personal data. If the reader of this message is not the intended recipient and/or you have received this email in error, you must take no action based on the information in this email and you are hereby notified that any dissemination, misuse or copying or disclosure of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by email and delete the original message. ------Original Message------ Hello Seattle Group: I am having some confusing formatting issues. Instead of displaying the content of a name or identifier field, my form shows the record ID. When I look at the format of my Look-up Table it seems correct. The first field is the name I want displayed. Any ideas what I am doing wrong? Any assist would be greatly appreciated. Dirk ------------------------------ Dirk Ruana ------------------------------Summarizing users
I'm wrestling with the lack of an option to use a Summary field to pull together a list of Users as defined on a child table. I'm hoping QB adds this type of summary field in the future. In the meantime though... The Goal:I want to enable the selection of stakeholders for each project, from a table of stakeholders that includes information including a User field matching them to their account. The Setup:I have a many to many relationship, as follows: Projects < Stakeholder Assignments > Stakeholders The Ask:I need a summary field at the Projects table that shows all User fields that were assigned to that project in the Assignments table. But there's no Summary field for Users. I know an alternative would be to report directly from the Assignments table on assigned projects, but the Projects table contains reams of data and multiple other relationships that I don't want to replicate as 100 lookups fields on the Assignments table. Plus I'd not have the ability to report on other Project child tables like financials and risks without also setting up a ton of other relationships. Any tricky ideas? I was playing with the idea of converting userfields to emails and then to text, summarizing that text, then somehow "back converting" those text email addresses to user accounts. But I'm not being successful yet. ------------------------------ Brian Richardson ------------------------------
