Édition

Partage via

Making Pages and Reports Searchable in the Web client After an Upgrade

  • Article

In Dynamics NAV, pages and reports were searchable in the Web client only if they were included in the MenuSuite. In Business Central, instead using the MenuSuite, pages and reports are made searchable by setting properties on the page and report objects themselves, specifically the UsageCategory property, and optionally the AccessByPermissions and ApplicationArea properties. The UsageCategory property corresponds to the DepartmentCategory property on MenuSuite items linked to page and report objects.

As a result of this change, after an upgrade from Dynamics NAV to Business Central, pages and reports that were previously searchable in the client, will no longer be searchable unless you set the required object properties.

You can set the properties of pages and reports manually (see Adding Pages and Reports to Search). Alternatively, the Business Central installation media (DVD) includes a Windows PowerShell scripted module called TransitionMenuSuiteObjectsForSearch.psm1 that includes the Set-ObjectPropertiesFromMenuSuite. The cmdlet saves each page and report included in the MenuSuite as a modified object text file that sets the UsageCategory, AccessByPermissions, and ApplicationArea properties to match the DepartmentCategory, AccessByPermissions, and ApplicationArea properties in the MenuSuite. The modified objects can then be imported into the database, either manually or automatically using the cmdlet.

Run the Set-ObjectPropertiesFromMenuSuite cmdlet

  1. Run Windows PowerShell as an administrator.

  2. At the command prompt, import the TransitionMenuSuiteObjectsForSearch.psm1 module.

    On the installation media (DVD), the module is in the WindowsPowerShellScripts\WebSearch folder.

    For example, run the following command:

    import-module -Name c:\dvd\WindowsPowerShellScripts\WebSearch\TransitionMenuSuiteObjectsForSearch.psm1

  3. The Set-ObjectPropertiesFromMenuSuite cmdlet has several parameters that you can set to change its behavior. To get help on this cmdlet, run the following command:

    get-help Set-ObjectPropertiesFromMenuSuite -full

  4. Run the Set-ObjectPropertiesFromMenuSuite cmdlet.

    For example:

    Set-ObjectPropertiesFromMenuSuite -RoleTailoredClientFolder "C:\Program Files (x86)\Microsoft
Dynamics NAV\130\RoleTailored Client" -DataBaseName "MySolutionDatabase" -OutPutFolder "C:\temp"

    In this example, the Dynamics NAV Development Environment (finsql.exe) installation path is C:\Program Files (x86)\Microsoft Dynamics NAV\130\RoleTailored Client, the database is named MyDatabase and modified page and report objects are stored to the folder C:\temp.

  5. If the cmdlet was not set up to import the modified page and report object text files, import them from the output folder into the database.

    See How to: Import Objects.

  6. Compile the imported objects.

    See Compiling Objects.

  7. In the Tools menu of the Dynamics NAV Development Environment, select Build Object Search Index.

    The pages and reports will not be searchable until you run Build Object Search Index.

See Also

Converting a Database - Technical Upgrade
Upgrading the Data