Well, the most important thing for creating something flexible is through consistency. ![]() If the user checks off “Unknown”, the related Value field must be empty.If the user puts a value in the Value field, the related Unknown field must be empty.If the user checks off “Unknown”, the related Value field must be grayed out.I love the Case statement but if I have to write too many potential tests, it can become overwhelming (and the amount of maintenance required is high!).įor the sake of organization, here is the problem in bullet form: If you have 2+ of these value field + unknown checkbox field, it would take a lot of work to hardcode all the field names in the script triggers and conditional formatting. Additionally, it would really help the user, visually, if the value field was grayed out when the “unknown” checkbox is checked. What we need to do to keep the data clean is make sure that a user can’t both enter a value and check the “unknown” checkbox. ![]() Now imagine that the user has to either enter the value OR check “unknown” if the user doesn’t have that information. Imagine having a layout that has a high number of date or number fields – think chemical analytics, data gathered before/during a surgery, or patient results from a blood test. ![]() So for the sake of efficiency (which is partly what this blog post is about), let’s get right to it! Ah! But before I do that, let me give you the spoiler of this blog article: Yes! There is a sample file at the end of the article! □ The Scenario If you show me something that needs to happen again and again, I’m immediately trying to find a way to create something flexible with the least amount of maintenance from me, the developer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |