This seems to be a problem for many partners and developers that have start working with Dynamics 365 Business Central on-premise in these days and this is not actually well documented in my opinion.
I think that you already know that when developing a page with the AL language extension for Dynamics 365 Business Central in the cloud, you need to set ApplicationArea and UsageCategory properties in order to see your page in Search.
If you open a Dynamics NAV 2018 page with CSIDE, you don’t have these properties available, while if you open the same page with Dynamics 365 Business Central on-premise, now you have them available:
What happens now is that if you create a new page in CSIDE with C/AL, set the ApplicationArea and UsageCategory properties and add that page to a Menusuite, often you can see the page in Windows Client search but not on the web client. Normally what happens is that you can see the page in web client search if you compile the Menusuite object, otherwise no.
If this problem occours, you have to build the search index (the Web Client search works differently now). To do that, simply open CSIDE, connect to your Dynamics 365 Business Central on-premise database and go to Tools|Build Object Search Index:
A process starts and after that you’ll have your C/AL objects in Search also in web client:
This process can be also performed via Powershell with the following command:
finsql.exe Command=buildobjectsearchindex, Servername=YourServer, Database=YourDatabase, Logfile=log.txt
Expect (hoping so) improvements on this topic… 🙂
P.S. this is related to C/AL objects. If you create extensions and publish them, the process of building the search index is automatically performed.