AlexWilkinson
Qrew Assistant Captain
Joined 7 years ago
User Profile
User Widgets
Contributions
Re: Create one Child Record per Year
I heartily endorse Mike's suggestion of a smart button that displays as "Add..." if no record exists and as "Edit ..." if it does. From a user's perspective, it's easy to understand and easily leads to the right behavior. I use buttons like that A LOT with excellent results. AlexRe: Rich Text formula 'expecting text' at the end of formula
Amy, When using <p> and </p> be careful to enclose them in quotes, before and after, like this ... [Some field] & "<p>" & [Some other field] & "some words or sentences" & "</p>" Same goes for other permitted HTML tags, such as <b> etc. Alex WilkinsonRe: Multi-select text field
FWIW, for situations like this, I've gradually come to the conclusion that (a) multi-select text fields are great for viewing a record and for reports, but (b) an array of checkboxes is a lot easier for data-input for most users, so (c) I create check-boxes plus a formula-multiselect field like this example: Split(List(";", If([Box1],"Box1",""), If([Box2],"Box2",""), If([Box3],"Box3",""),, If([Other],"Other",""), "" )) Then you would not need a checkbox for "No" or a form-rule. You just modify the formula-field by making the List() portion above (without the Split) into a var ... like this var text mylist=List( ...) Split( If($mylist="","No",$mylist) ) Alex WilkinsonRe: Dynamic-Displaying Button in One Field
Aidon, Here's an example of how I handle similar needs for "conditioned" buttons - one which take various actions and have various wording or styling depending on other fields on the record. In this example, the user will be able to add a contact where the record has data about a new person (e.g., a new, unrecognized email) and about an organization whose web-domain is either know to the app or not known. Accordingly, the button displays on a report either as "Add Person to KNOWN Organization" or "Add Person to NEW Organization". The button uses a URL computed as a var in portions of the formula field not shown in the screenshot above. It also uses custom styling that is defined in app-wide variables (the three "[customButton...]" variables. This is a convenience to make it easier to standarding the app's buttons without constant cut-and-paste. Alex Wilkinson AlexRe: New problems entering address?
One solution would go like this: 1) In your app, create a new table with two fields, the two letter code is one, the state name is the other. Both are required & unique. Call this table "State Lookup" or something similar. 2) In your pipeline, insert a new Query step which finds the record in the new table that has the two letter code, and returns that plus the state name. 3) In the existing step of your pipeline that creates a new address, use the state name that the new step found. AlexRe: New problems entering address?
Jeff, I actually think a dropdown for US states is an improvement. It prevents errors by all those users who don't know whether MI is Missouri, Mississippi, Minnesota, or Michigan. But I agree that the dropdown should not be the last work. My suggestion is twofold: (a) In the dropdown for US State, show both the postal code and the full state name, so that the user can query based on either of those. (b) Revise the Region/Postal code values for the US to be a combination of the two-letter state postal code plus the zip code. So the value of the field would be, for example, NY 10017. Alex WilkinsonRe: Huge Oversight with New Forms?
There's an exception to the rule for that parent and child forms must both be on new-style or both on legacy-style. Scenario: You are editing a previously save record in a new-style form and you want to add a parent with the pop-up-then-refresh method. That works if the pop-up uses a legacy-style form, but not if it uses a new-style form. Same is true if you use %%rid%% on an unsaved new-style record to which you are adding a parent. Alex WilkinsonRe: New Form Issue: Adding Child record and redirecting back to parent form
Annetta, sorry, one more comment and one clarification: - A custom rich-text button that pops up a new window and then, when the pop-up closed, updates the original record, does not work if the original is a new-style form. This one has been escalated. - The problem with &NextURL may be sporadic or may depend on some other factors. I do not know whether it has been escalated. Alex
