ContributionsMost RecentMost LikesSolutionsChatGPT like search engine? Hello all. Long time no talk! Anyway, I started using QB for my company in 2006 to records problems/solutions found in the field by our field service engineers related to our products. We know have 65K+ cases! Of course now the issue is to search for similar issue in this immense database! For instance, it will be useful four junior engineers confront with similar problems in the field. At least to give them a list of similar issues cases to help them fix the tool. But as you can imagine a QB keyword Seach type is almost useless with the database is that large. One because if the keyword is not present (or miss-spelled) then QB will not find the similar cases. Or sometimes it returns 100's cases! For instance say the "beam is unstable" and "the beam is What we need is a semantic search option with QB. Or even better a tool like chatGPT applied to the 1000's of cases already in the databases. I have been experimenting with chatGPT, chatPDF and also with CLAUDE (different from OpenAI company) and got some great results. But it means I needed to export a version of the QB tables (repair database) into a PDF and use one of those tools above. Which also means we cannot have an update system since dozen + are added by our FSE Worldwide! Anyway, I just wanted to start the conversation about large language models (LLM's like chatGPT) applied to QB. Of course, this will not be limited to Q/A of a QB applications. They could also be used to analyze QB data and so on. Will love your point of view and hopefully QB team to look into it! I think SaleForce has already integrated AI in their system.. Cheers. Mo ------------------------------ Mohamed Bennouf ------------------------------ Re: QB and semantic search (vs keyword based search)Hello Mark Thank you SO much for your response. I really appreciate that you always answer so fast! Love it! Yes you are 100% that not many people know about OR and AND. Even me only discovered only few years ago! But as you said, every time we have an new employee we have to train them over and over. Unfortunately even with the addition of AND and OR keys, we still have to deal with people describing things differently (or I said misspelling words) Only semantic search can deal with this type of issues. I will look into your other suggestions. That may work but I am hoping that QB will come up with a semantic search tool to deal with huge text corpus. Of course I am sure most people may use QB differently from us. We do use QB to collect field repairs but also allow our FSE to request parts and send notification when the parts ships. We used QB for many many processes in our business. Search is mostly to bring even more values since it will help our FSE’s to speed up troubleshooting of the customers tools in the field. In any event, thank you Mark! QB community is lucky to have you around! Cheers Mo QB and semantic search (vs keyword based search)Hello all Happy New Years! Even so i am not longer involved with QB support I am still interested of what QB can do. For instance in our company our service databases has 70K repairs cases (problems/solutions pairs) When we first started using QB back in 2006 we could not imagine having so many cases to search! But it is becoming a big issue. To the point where our engineers are less and less incline to search our QB to support their daily job which is to troubleshoot our customers instruments. The reason is even a targeted search returns 100's cases which need be look at manually to find what they looking for. Worst if they don't enter the correct term (misspelling) because they could miss the correct tool diagnoses that could have help them. That is why searching a large corpus of text (text fields...problem/solution) is not doable anymore. Our QB is gold mine but we need a better shovel :) Anyway I have been looking at machine learning and NLP (for instance semantic search) to try improve our QB database search. Obviously the current "keyword" based search that QB is using is no longer working for us. I think using advanced NLP tool could help. I am curious if anybody here has looked into semantic search? Or at least at more advance search methods. I think it is a big problem when you are dealing with free text inputs and have huge number of records. My hope of course is that QB will look into it and propose and integrated solution. Rather than us coming up with our solutions since this will means extracting our data and then use an external advance search process. It won't be seamless anymore I guess. Will love to get the community ideas/though about this. Also, finding out if I am the only person who find the current search feature lacking when it comes to search for a large text corpus. Thank you for your time. Mo ------------------------------ Mohamed Bennouf ------------------------------ Re: cross application searchHello Mark. I am SO SO sorry for the delay. I completely forgot that I ask that question so long ago! I no longer manage our Quickbase so it was out my radar (or maybe just age :) I will pass your answer to our IT people (who now deal with our QB) Thank you again for your help and sorry for the long delayed response! Mo ps: In my more personal note, I am so happy and impress that you still helping people here. You are the BEST! ------------------------------ Mohamed Bennouf ------------------------------ Re: cross application search Hello David. I was searching a cross applications search feature and found your question and your response. I have 4 more or less same applications that records field engineers repairs (USA, FRANCE, JAPAN....) and now need to do a search for past repairs globally. Of course the smart way would have to have combine all those apps in one. But management at the time (2006) wanted to customize the look for each app) I want for now to add a global search to the USA QB app so I can search not only the USA QB but also FRANCE,JAPAN.. QB for a repair. It seems that you were able to make it work by adding a formula field that serialize info from the parent's table? Could you explain the process in more details if you won't mind? Would in my case, QB USA be the child app and the other worldwide QB the parents? I guess i should forget about all the other QB but one (like FRANCE) since I am assuming if I can search QB France from QB USA then I can do the rest of the QB's later. Sorry for the long message. I just wanted to setup my issue. Thank you again for any suggestions. Mo ------------------------------ Mohamed Bennouf ------------------------------