BullseyeBullsey
Qrew Cadet
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Add Record"" button redirecting after saving in mobile... when it's not supposed to?
The formula you included sends me somewhere else, and I needed to have the new record ID to keep me on the new record I created. I was able to play around with it a few hours ago, and managed to make it work on iPhone but not Android. URLRoot() & "db/" & [_DBID_ORDERS] & "?a=API_GenAddRecordForm&_fid_17=" & URLEncode ([Club Name])& "&NextURL=" & URLEncode(URLRoot() & "db/" & [_DBID_ORDERS])& "a=dr&rid=API_DoQuery&RIDs=1&query={'1'.AF.Now()-Minutes(2)}AND{'5'.CT.User()}AND{'17'.CT.[Club Name])&clist=3\noptions=num-1" I'm very limited with URL coding, but that's what I have if anyone is looking up this issue. Thanks Sharon.9Views0likes0CommentsAdd Record"" button redirecting after saving in mobile... when it's not supposed to?
When a user creates an order, they need to stay on that page to add another record related to an order. This has always worked fine on the PC, but for some reason our mobile version has been returning people to the previous page after they save the order: URLRoot() & "db/" & [_DBID_ORDERS] & "?a=API_GenAddRecordForm&_fid_17=" & URLEncode ([Club Name]) It definitely does not have the & "&z=" & Rurl() added to the end. I'm not sure if there's any way to fix this by using a different link or form for mobile users? I appreciate any help or insights.Re: Quick Base App Builder & Expert Builder Certification Now Live
You guys should probably update this page with the correct expiration date. First clue was that June 31st doesn't actually exist :) https://university.quickbase.com/series/validate-and-promote-your-quick-base-expertise?_ga=2.2520291...17Views0likes0CommentsPublic App - Guestbook? (and more)
We would like to have a public facing App for our customers where they can find links to our current catalog, limited offers, and special products. Several questions: Would it be too un-secure to have a single login (e.g. preferredcustomer@_ourdomain.com_) for all customers? I know there is a "everyone on the internet option," however we would prefer it to be a more exclusive feel. We would like to track who is viewing the app. Is there an easy way to automatically log this? Or, could we have them land on a guestbook form where they enter their business name, and automatically hop to the home screen? Our client base is usually older people, so simplicity is much preferred. _If_ we eventually needed more attachment space (right now we don't think we'll even touch our 50 GB), is the cost for adding space a one-time deal or is it monthly? If it's monthly, can we request a smaller amount than the 100GB add-on? I would appreciate any suggestions on implementing this. Thank you!Re: Who is the new map provider that is being tested?
Hi Brian, thank you for responding. Yes, we are aware that this is just for testing now; the issue here is that there is going to be a major, seemingly random change. I'm sure QB has a good reason for it, but this has implications from those of us who just "point and click" without code to those who utilize more complex codes/scripts. Again, per my questions above, how will this update affect us if we rely on the quick link to Google Maps for our daily workflow? As noted in this thread, there are concerns on how this drastic change will affect users who are tapped into Google for things other than just looking at the map. I appreciate your insight.4Views0likes0CommentsRe: Limitations of QuickBase - Things that Cannot Be Done Natively
UserVoice is definitely not well implemented. I agree with many of these, but I may be able to help with one. For the "Cannot delete or reactivate a user once created," you can change their role to "none," which will lock them out, assuming the app isn't open to the public. You can also check or un-check "Show in User Picker" so you do not assign them to new records in your app. However, if you would like to reactivate them, you can simply reassign their role and check "show in user picker." They will maintain all of the same access as before. This might not work if you give access by groups (we don't use that feature, so I wouldn't know), but has worked well for our purposes. Hope this helps!28Views0likes3Comments