Hello @WarrenBelz,
Thanks for coming in to help. I just wanted to try and sort this out a bit more, as I'm a bit confused/having trouble on the approach to this.
My original datatable Items formula is this:
Filter(
'List1',
(IsBlank(Column1Textbox.Text) || StartsWith('Column1', Column1Textbox.Text)) &&
(IsBlank(Column2Input.Text) || StartsWith('Column1', Column2Input.Text)) &&
(IsBlank(Column3Input.Text) || StartsWith('Column3', Column3Input.Text)) &&
NOTE THIS FIELD IS NOT YET SET UP IN SHAREPOINT -> // (IsBlank(Column4ComboBox.Selected) || Column4.Value = Column4ComboBox.Selected.Value) &&
(IsBlank(Column5ComboBox.Selected) || Column5.Value = Column5ComboBox.Selected.Value) &&
(IsBlank(Column6ComboBox.Selected) || Column6.Value = Column6ComboBox.Selected.Value)
)
With this formula, I am currently able to filter my sharepoint list by any combination of inputs into the 6 fields and see the filtered data in the datatable. I need the Search function for the Column 2 and Column 3 text inputs so that I can get a filtered result based on any data put into the input. Column 3 can be any combination of keywords someone would manually type.
Just substituting Search in for the StartsWith for Column 2 & 3 yields "Invalid argument type. Expecting one of the following: Boolean, Number, Decimal, Text, Untyped Object."
Since I do not know the size of the list, are you recommending that I use your blog's Collect All Records In List method? How does this work with multiple search inputs? I was recently informed that the list may never exceed 5,000 or even 2,000 records (although I'd prefer to be set up for the possibility of more than 2,000 records). Should I worry about the performance impacts of the collect all method? I think my user's would be very upset to see a drastic hit to performance.