2.3.  Full-text search combined with geometry and ERP values

With ERP/PDM integration, there are additional possibilities in compare to standard search.

[Note]Note

All basic search options are summarized under Section 3.1.6.4, “ Search methods ” in PARTsolutions user manual.

Information on the full text search [Full-text search] (syntax) can be found under Section 3.1.6.4.3.2, “ Full text search: Detailed search options ” in PARTsolutions user manual.

[Note]Note

For ERP integration, the user interface is configurable depending on roles.

Only visible elements are searched in the respective role.

=> That's why also the search results are different.

Example 1:

In a full-text search [Full-text search], projects and the link database are always searched together. Even if there are several search terms, it does not matter whether hits are found in the project file or in a column of the link database.

[Note]Note

In a standard search with simply entered search terms one after another please regard that ALL terms have to exist anywhere.

[Tip]Tip

For very specific searches, such as for ERP numbers or special descriptions, it is advisable to search at line level. To do this, select "Search for individual parts [parts] ".

Search with "hexagon head screw superduper":

Result: Click on more [more...]... to see details.

You will see that "hexagon bolt" has been found in the characteristic attribute table and "superduper" in the LinkDB .

In the table you can also see that the entry has been made both in the project file and in the LinkDB.

[Note]Note

The filter icon top left is signalizing that the table has been restricted. If you want to see all rows, click on the icon.

Example 2:

In this example, two search terms are used in conjunction with the Boolean operator OR.[4].

Search with "hexagon bolt OR superduper"

Search with "hexagon bolt OR superduper"

[Note]Note

Don't forget to search for part families and individual parts [parts and part families] this time. The search term "hexagon head screw" would unnecessarily produce a huge number of hits.

The particularity is again that the one term will get hits in project files and the other hits in the link database.

Search:

sechskantschraube OR superduper

When using OR it is sufficient, when of the two terms gets hits.[5]

That means projects are found either containing the term "hexagon bolt" OR the term "superduper", independently of whether the term has been found in the project file or in the LinkDB.

Search results [Search Results]:

The result list of course includes hexagon bolts, but also a hit "head cap bolt".

Search with "hexagon bolt OR superduper"

Search with "hexagon bolt OR superduper"

The reason is that the project with head cap bolts has the term "superduper" in the LinkDB.

[Note]Note

Please regard - especially when adding a term in the link database manually - that the ERP index has to be created anew.[6]

You can find the corresponding command in PARTadmin -> Index management [Index administration] -> Context menu command Generate index for link database search [Create link database search index].

The blue database icon signalizes that the LinkDB index is available; otherwise it is grayed out.

The blue database icon signalizes that the LinkDB index is available; otherwise it is grayed out.

The index includes all role information.




[4] Boolean operators could also be used with earlier versions.

[5] Without operator or when using AND both terms had to get a hit on respective row.

[6] In a productive environment this will happen in an automated nightly update process.