Forum Discussion
..... the alternative is to review your form and figure out how to use form rules to just have one form.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------
Yes, that should work in most cases. We found the logic required to deliver different UIs based on attributes of the record was becoming extremely complicated to implement and test. We also had to place fields on different tabs depending on these attributes, which meant the single form route wouldn't work (AFAIK :)).
------------------------------
Jeremy Anson
------------------------------
- MarkShnier__You2 years ago
Qrew Legend
Ya, you need to decide on the least worst option. Formula fields can be on the form in multiple places on Legacy forms. Not sure about New Style forms.
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com
------------------------------ - ChristineK2 years agoQrew CadetGreat thoughts on all of the above. Before I switched over to having a formula field to pop up that form, I used the QuickBase Junkie's template for setting up a "toggle switch" between the two forms – hers was meant to go from "New" to "Old", and for me, I have two specific new forms.
Mark - thought about what you mentioned on using one form. The issue I run into is depending on the "lens" you're viewing from, the layout of info is different, and so it just felt like welp, since I can't put a field in multiple locations on a form and have it change anywhere you change it, the alternative is just, click here when you're working on the project through this lens.
I might go back to using the "toggle" switch, but having it pop out into an editable version of the other form feels like the "least worst" option haha.
Confidentiality Notice:
This e-mail, including any attachments is the property of Trinity Health and is intended for the sole use of the intended recipient(s). It may contain information that is privileged and confidential. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please delete this message, and reply to the sender regarding the error in a separate email. - ChayceDuncan2 years agoQrew Captain
Christine - how big is the form? This is not what I would consider a 'good' option - but if the layout is important - you could create multiple entries for the same field - and then consolidate them using a formula. So for example lets say you have a Price field that you want in different spots on the form - you could have Price (A) and Price (B) and then create a consolidated Price formula field that brings it back together. That works if you only have a handful of fields but an option nonetheless.
------------------------------
Chayce Duncan
------------------------------ - ChristineK2 years agoQrew CadetOh that's an interesting idea but probably not viable for this particular use. So we work with hospitals, and there are probably 100 fields of info on the "Master Hospital Dashboard", and then a "Logistics" form where some of the high-level details are useful (when did we become partnered? What types of services are they going to receive?", alongside each logistic datapoint. Early on, I just created a separate "Logistics" tab that was meant to essentially be the way a user (client manager) would access that information. But it's really nice to just see the full Logistics sheet as it is displayed to our actual clinicians, who don't edit any of this info. Also to display it that way to the hospitals themselves when doing a screenshare on a client check-in call.
Confidentiality Notice:
This e-mail, including any attachments is the property of Trinity Health and is intended for the sole use of the intended recipient(s). It may contain information that is privileged and confidential. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please delete this message, and reply to the sender regarding the error in a separate email. - ChayceDuncan2 years agoQrew Captain
Just thinking through one other option, it would be difficult and pretty annoying to implement - but if you wanted to have different layouts and also have different 'edit' forms based on different criteria - you could try something where the Default form is just one big rich-text formula rendering of the form. Basically just take all your info and build out the form to display in one massive rich text. Make that the only field on the form so regardless of how your user lands on that form it's always this same non-editable field.
In your rich-text field - you could insert hyperlinks that do pop up's of different forms that correspond to different sections. So if you had Section 1A for this type of form entry - user sees the data you want to show and if they want to edit, click a hyperlink and it pops out a different form specific to Section 1A. Do the same for Section 1B etc. It makes the 'edit' experience more like a series of modals/pop ups which is not a common QB interface, and make's it complex to administer but would allow you to insert all sorts of complexity into how users view and edit any type of record.
------------------------------
Chayce Duncan
------------------------------ - ChristineK2 years agoQrew CadetOh that is interesting! We really only have those two forms (and I'd LOVE to build the "Logistics" form into something that just pulls directly into a child table without having to pull in each individual linked field (there are probably 50 or so linked fields). Maybe a default form could be basically two buttons - to launch either of the two other forms, based on what you're needing.
Confidentiality Notice:
This e-mail, including any attachments is the property of Trinity Health and is intended for the sole use of the intended recipient(s). It may contain information that is privileged and confidential. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please delete this message, and reply to the sender regarding the error in a separate email.