ContributionsMost RecentMost LikesSolutionsRe: Dynamic Filter - Default Date Range? (without filtering) You would have to let the Users edit the filter that drives the initial report which is usually not desirable. I have thought about this problem before but never submitted it to Quickbase as a development idea. You can do that with their User Voice forum, but it is a long road before things get done there. Re: Hide user id while exporting You can make a report field and use the function UserToName(User x) where "User x" is the field in the table that you are exporting now. Re: Posting from an HTML form directly to Quickbase Can you share what you used for a prompt? Re: Posting from an HTML form directly to Quickbase FloridaBased, It is about 30 degrees here, so I am jealous of your location. Let me suggest a small variation on your plan. Send the data to a standalone QB app that does not need a User Token. Then use a Pipeline to send that data to your main application. I would even set up some cursory review of that data and check box "Approved to Export" or something that would fire the Pipeline. Now you do not need to authenticate from your HTML page and the code should be much simpler. Re: Proxy fields One more thing. I suggest you spin up a new application and build the example in the article. It will help you alot to do that one and then apply the lessons learned to your real application. Re: Proxy fields Absolutely. There is a feature called a Conditional Drop Down. Here is a link that explains it in more detail. https://helpv2.quickbase.com/hc/en-us/articles/4570407379604-How-to-add-Cascading-Dropdowns?_gl=1%2A95t3eh%2A_ga%2AMTMyMDQzNDY2LjE3NDIwNzA1Mjc.%2A_ga_YZ6780317K%2AMTc0MjU3MzM3Mi4xMy4xLjE3NDI1NzM0NzMuMjkuMC4w Re: Time Zone change I would build your Transportation table differently UTC Offset would be a Numeric Field Local Time Pick Up would be a Date/Time field [Pick Up]+Hours(7)+Hours(UTC Offset) This takes the MST Time then converts it to UTC and then to the time zone of the local airport. This does not solve for DST. Re: Time Zone change Expanding on Mark's answer, you should have two offsets. One for Standard Time and one for DST. There are places that do not change the clocks, particularly Arizona does not observe DST. Same with parts of Indiana and so on. Then you make an If Statement in the Pick Ups table to use either offset on whether or not Today() is Standard or DST. Re: Calculation/Performance Limits Inquiry Mark, In this particular business case, the child tables hold data from outside suppliers that structured completely different from each other. However through a lot of If and Case statements, they can be synthesized down to Normalized Data. The Master table through the summary fields tells the client about the Normalized data at an aggregate level from all of the child tables. It is ugly. Re: Calculation/Performance Limits Inquiry Curtis, A different way to tackle it would be to use something like Tableau or PowerBi. Inside of those you can write real SQL expressions that are much faster than using the QB reports. It is also more difficult than QB, but there is always a trade off.