ContributionsMost RecentMost LikesSolutionsRe: Jinja for User List field I think the original post was just trying to take one user from a User List and put that user ID into antother user tpye field. This is easy, unless there are more than one users in the user list. In that case, you have to somehow decide which one to select and add to the single user field, and I can't help with that. If all you want to do is update a List - User field with another user, than just add the user id into that value in the Pipeline, and it will update the single user. My problem was that I was trying to iterate over a loop of users in a List User field, and then access the email property for each user to make a list of the email addresses for the List - User field. I ended up solving this by using a Formula - Text field to just list the user emails for me, and then I access that field in the Pipeline using Jinja. Re: Jinja for User List field And now I am also looking for this too. I can only seem to get the user id string out of this, but not the email or username. Re: Pipeline GUI Issues Did anybody else notice that the Product Manager made a quick appearance and then dissapeared again forever? It must be a bit embarassing given that now the new Pipeline "designer" is available in Beta, and it has already corrupted 3 of my existing Pipelines PERMANENTLY. I'm sure one of the development team members could send my source YAML over to re-create, but I am wary enough that I exported the YAML on my own before even touching their new tool. So thankfully I had a backup for all 3 corruptions. We are expected to waste our time (and the time of our employers) being the guinea pigs on this beta tool. It offers some much needed improvements, thankfully, but is still a bit of a mess once you really dig in. I hate to say that for now it's still better to use the clunky "old" original Pipeline builder. Re: New form Print record It does seem like adding ifv=1 now works on the new forms, so this could help with printing a more clean page. It also could mean that the "new" print function is not far behind. Oh Quickbase. Re: New form Print record Two months later... still waiting for them to finishing baking this for us! Still can't use: ifv=1 in the URL just to embed a form somewhere - like I've done for years with the old forms. They have fixed a lot of stuff, but that just tells me even more that it was "half-baked" on release, because there was SO MUCH to fix in the first several weeks. Re: How to stop user(s) requesting permission to create applications billed to the account There is a "new" request for this people can upvote on. There may be older ones I didn't see too. https://feedback.quickbase.com/app/#/case/292634 Another one: https://feedback.quickbase.com/app/#/case/123639 Re: New Form Builder Rules - Where is the bug list? It's frustrating dealing with these form bugs. And important to understand there is a difference between Support Cases (specific to your organization and apps) vs. "Feedback" (which is applicable to all Quickbase Users and Apps). Brian Seymour,07-06-2023 12:51 While I agree it is important to remember the different between a Support Case and Feedback, it's also important to remember the difference between a bug and feedback. Perhaps in the interest of time, the previous post confuses this a little. Feedback insinuates a suggestion to make the product behave differently than it currently behaves. You should not submit a Bug here simply for the purpose of allowing other users to see it within the Feedback system. A Feedback example: in the New Forms, I believe some great feedback is that the embedded Report feature should not display the large space-consuming button and search widget by default. The user should be able to disable it. Bugs are issues with the software and underlying code or workflows, and should typically be submitted as a Support Case inhibiting the user from using the software platform. We shouldn't really have to provide Feedback for a bug, as it should be addressed and fixed ASAP by the Product Development team. For example, some of the Form Rules in the New Form become corrupted with a "white screen of death" that cannot be recovered from, and this make the product essentially unusable of this happens. The previous post might almost be suggesting that a Support Case is not applicable to all Quickbase Users and Apps, while that couldn't be further from the truth. The bugs I have submitted through the Manage Cases link are applicable to all users of the New Form product, and were quickly acknowledged. Just because all other users cannot see my Cases does not mean they aren't applicable to all users - since QB will ideally fix these bugs I submitted for ALL users. But you can't track the status of bugs I've submitted with the design of this system. Re: Remove "manage support cases" link from help button drop-down I think the key is in the follow-up screen shot I posted. You must check the box indicated. Re: Remove "manage support cases" link from help button drop-down Also, when setting Role permissions, you can check to hide the UI for "Help" and set this on a role by role basis. Re: Remove "manage support cases" link from help button drop-down Have you confirmed that other users can actually see the Manage Support Cases link? I believe that in my realm/organization, most users cannot see that anyway. You have to have a certain level of permissions to see it.