MarkShnier__You
Qrew #1 Challenger
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: Date Input
I am going to interpret your question that you have records with a single date on them. Then you want to let the user run a report where they can specify a range of dates. So just create a regular Table report, which is just a list of records and in the filter section select where the date is or after And then it should give you a drop-down choice of ask the user Then put that filter on the report, a second time as a filter and this time where the date is on or before and again choose ask the user. The effect should be that when you run the report, it will ask you those two questions and you should be able to answer them and get results.1View0likes0CommentsRe: Formula URL - Edit then Add
Try this URLRoot() & "db\" & Dbid() & "?a=er&rid=" & [Record ID#] &"&dfid=11" & "&NextURL=" &URLEncode(URLRoot() & "db/" & Dbid() & "?act=API_GenAddRecordForm&dfid=10" & "&_fid_6=" & [Paragraph] & "&_fid_7=" & [Publication] & "&_fid_8=" & [Description] & "&_fid_11=" & URLEncode([Staff Contact]) & "&_fid_17=" & [Effective End Date] & "&_fid_19=" & [Record ID#])9Views0likes0CommentsRe: Logging causes dynamic rules to not work
You can make a formula text field to parse out the most recent update. Then base your form rule on that field. The field should be put on the form even if hidden by a firm rule so the firms rules can see the calculated field. Trim(Right([my update field],"]"))5Views0likes0CommentsRe: Forced to use new dashboards?
Actually I did a little more playing around with new dashboard widgets and they are growing on me. I realize since the box is a little or a little deeper that I can now put my labels for what the Widget represents inside the box and free up a lot of space I used to use up a whole box for the Rich Text label.46Views0likes0CommentsRe: Looking for State abbreviation to full spelling formula
.. and here is another one. I forget offhand why I had to do the upper and lowercase thing but I think it had to do with inconsistent data entry when users typed in the state name and the capitalization was inconsistent. But I see I did something different for the states which had two names. I have a feeling I should have just use the two word name method for all the states. var text StateRaw = Trim([Address: State/Region]); var text State = Upper(Left($StateRaw,1)) & Lower(NotLeft($StateRaw,1)); If( $State="Alabama", "AL", $State="Alaska", "AK", $State="Arizona", "AZ", $State="Arkansas", "AR", $State="California", "CA", $State="Colorado", "CO", $State="Connecticut", "CT", $State="Delaware", "DE", Upper($State)="DISTRICT OF COLUMBIA", "DC", $State="Florida", "FL", $State="Georgia", "GA", $State="Hawaii", "HI", $State="Idaho", "ID", $State="Illinois", "IL", $State="Indiana", "IN", $State="Iowa", "IA", $State="Kansas", "KS", $State="Kentucky", "KY", $State="Louisiana", "LA", $State="Maine", "ME", $State="Maryland", "MD", $State="Massachusetts", "MA", $State="Michigan", "MI", $State="Minnesota", "MN", $State="Mississippi", "MS", $State="Missouri", "MO", $State="Montana", "MT", $State="Nebraska", "NE", $State="Nevada", "NV", Upper($State)="NEW HAMPSHIRE", "NH", Upper($State)="NEW JERSEY", "NJ", Upper($State)="NEW MEXICO", "NM", Upper($State)="NEW YORK", "NY", Upper($State)="NORTH CAROLINA", "NC", Upper($State)="NORTH DAKOTA", "ND", $State="Ohio", "OH", $State="Oklahoma", "OK", $State="Oregon", "OR", $State="Pennsylvania", "PA", $State="Rhode Island", "RI", Upper($State)="SOUTH CAROLINA", "SC", Upper($State)="SOUTH DAKOTA", "SD", $State="Tennessee", "TN", $State="Texas", "TX", $State="Utah", "UT", $State="Vermont", "VT", $State="Virginia", "VA", $State="Washington", "WA", Upper($State)="WEST VIRGINIA", "WV", $State="Wisconsin", "WI", $State="Wyoming", "WY", UPPER($State))0Views1like0CommentsRe: Updating predecessors in a pipeline
Ok, I re-read your original question now I realize I should've answered with a little more thought put into it. The coffee master detail is very powerful in part because it can also deal with the issue of predecessors. But in order for that to be legal you need to have a couple of requirements. One is that the projects and tasks all need to live in the same tables. In other words you would have to designate certain projects to be special template projects and therefore their Tasks become a special tasks which can be used in the copy master detail. You cannot have a separate table to hold the template tasks. Typically what you do is you set up the special projects with their special tasks and you flag them as being template projects. Then you use permissions to make sure that your regular users can't accidentally mess around with your templates. Know how much data and kind of investment you already have in your current structure but it's a pretty simple test to set up a Template Project in your Projects table and hence a set of templated tasks. Do the predecessors manually, and then do a test with the API or in fact it may be easier to have your users push a button which can be created with the CopyMaster Detail wizard helper found in the App management Settings for the app. The use of Copy Master detail it's also very particular that the structure of the app for any of the tables involved must be purely hierarchy. By that I mean one parent has many children and their children can have children of their own. But you can't have any "incestuous" relationship like relationships between parents for example. I imagine that you would want your users to be able to be sitting on a project record and be able to select the special template project which has the template tasks. Soon as you do that you violate the pure hierarchy of relationship. As I recall I think I got around this in the past by making a connected sync table of the templated of projects. By that I mean just a connected sink table of the template project names and of course the record ideas will come across automatically. Of course the record ideas of your connected same table will match perfectly with the record IDs in your projects table. They will be identical. So then you would use the record ID of the related template record as kind of a proxy representation for the record ID of the project template record in your main projects table. Now I hope that's all clear and feel free to post back with any questions or email me directly since currently they are debugging this new Forum and I am not receiving any email notifications when you do updates. If you come back and see you have too much invested in your current structure to do what I'm suggesting then while I'm not saying that anything is impossible, let me say it's going to be extremely difficult to create some kind of crazy pipeline which will set up the predecessor records. That copy master detail functionality is really ancient code under the covers at QuickBase that does it's magic and it would be very hard to replicate with a fancy pipeline0Views0likes1CommentRe: Saving a record
I presume you are using the add Child button which is sitting on top of the embedded report of children on the parent form. One option is to edit that report element so that it does not show the add child button. so deselect Show create record button Then put the add child button on the form directly and change the code to comment out the last part so that the code it will look like this. URLRoot() & "db/" & [_DBID_CHILDREN] & "?a=API_GenAddRecordForm&_fid_7=" & URLEncode ([Record ID#]) //& "&z=" & Rurl() That way, when you save the child record it will land the user in View mode on the child record4Views0likes0CommentsRe: Forced to use new dashboards?
One tricky thing I noticed which comes into play when you have a whole dashboard full of little key measure widgets (ie a gauge chart report which renders as a single colored number). Typically you put the widget and you use a text box before the widget to explain what the key measure is. I see you have to be very careful on New Dashboards because now that these widgets dynamically jump all over the place as you move them around it's very easy to accidentally separate the widget from the text box that explains what key measure of the Widget refers to. You could easily end up with a whole column of Key Measures which are misaligned with their labels. Also, the new widgets are arguably prettier, but are longer in height, so the lower ones are not visible without scrolling. There is certainly an argument to be made for giving Admins the ability to select which style of Dashboard they want to use.40Views0likes0Comments