ContributionsMost RecentMost LikesSolutionsBug Report With Grid EditGood afternoon all - Found what I think might be a bug to bring to your attention. I create a new Grid Edit report, and specify specific report columns. Upon the initial save of the report and viewing, it shows exactly the columns I specified. However, if I ever click the save button at the top of that report, it appears to reset my column specifications and show all columns. The settings of the report still show it configured for my specific columns, but no amount of tinkering can resolve this in my efforts. EDIT: Images are kind of out of order. Image #1 is the report config. Image #3 is the initial column headers, matching the config. Image #2 is the column headers after clicking save a single time. ------------------------------ Josh Payette ------------------------------ Re: Feature requests from a newish userI was responding before your second response came through - what you mentioned about redeveloping the forms makes sense, and I will use the appropriate feedback channels. I wanted to make one more post to acknowledge your follow-up. ------------------------------ Josh Payette ------------------------------ Re: Feature requests from a newish userThanks for the response, Mark! What you said makes sense. The reason I did it the way I did is because my Facilities table had more columns than facility name, but I wanted user selection to only be the facility names. I didn't recall seeing an ability to make the record picking work in this way, but if it's possible I'll take another look. Regarding the 100 item limit to select boxes, I am still not sure whether the limitation actually does anything, particularly if it's a field pointing at another table. All across the web we have select boxes with far more options. Additionally, my select box does have over 100 items in it since I have it point at an empty table for values, then use a pipeline to build out that table, so the 100 limit is not truly a hard limit within Quickbase. It seems to exist just to exist. Ultimately, not a big dealbreaker for me! But like you said, perhaps the record field is the better tool for this, so I will check that out. I appreciate your feedback and the guidance you provided as it relates to the proper way to submit feedback as well as the pain points I mentioned in the original post! ------------------------------ Josh Payette ------------------------------ Feature requests from a newish userGood morning all! I'll start by saying if there is somewhere better to put feature requests, I will happily submit this through a formal channel! I have been building out a new system on Quickbase and hit a few pain points that I thought I would mention in case it hasn't been brought up before! Select fields being limited to 100 items. This limit seems arbitrary, as I am able to use a pipeline to fetch data, write it to a table, and use that table data as the source for a select field. What the limit does do, however, is it make it so that I cannot make changes to the field without the "only 100 items allowed" error. This forces me to delete data from the table, make changes to the field, then rerun a pipeline. I'm not sure of the practical reason for limiting to 100, but I would hope to see this removed. To give a practical use-case, we have a field where we allow our users to select which facilities their report is in reference to, allowing selection from a list of facilities. We currently have 147 facilities. Dynamic form rules layout is pretty hard to parse in my opinion. Using new lines to structure the various parts of the rule to make it more readable (like code indentation) I think could help. Additionally, allowing resizing of the dynamic rules list portion could help! These are the only pain points I've found myself having so far. Outside of that, I'm impressed by how intuitive and powerful this system is. My thanks to the development team for the hard work! ------------------------------ Josh Payette ------------------------------