Our 3D CAD supplier models have been moved to 3Dfindit.com, the new visual search engine for 3D CAD, CAE & BIM models.
You can log in there with your existing account of this site.
The content remains free of charge.
PARTproject -> Edit project -> General tabbed page -> Variables -> Variable with order number and/or Variable with type code
Note | |
---|---|
|
In PARTdataManager, you can switch between normal Full-text search and search for Order number or type code .
The search method Order number or type code should be used when explicitly searching for it. Due to uniqueness this search will always directly lead to the desired result (if the catalog is accordingly prepared).
This method does not only lead to desired result when searching for a fixed Order number / Type code, but also then, when it is composed by values from value range variables and in fact both for simple and for complex combinations.
Note | |
---|---|
Catalogs may contain simple projects without value ranges or with value ranges and those again can be build more simple or complex. In order to detect which cases exist in a catalog the Resolve check should be performed. See Section 5.8.2.1.15.18, “Reverse search ‒ Resolve check (automatic) ”. |
Simple project without value ranges
Project with value ranges which can be resolved by inclusion into the full-text search index
The inclusion
into the full-text search index is possible if there are less than
25.000 possible combinations per project or 50.000 per catalog (default
limit) in addition to the standard rows. Setting the limit is performed
via configuration file %cadenas_setup%/partsol.cfg
.
On this please see under Section 3.2.18.8, “Limit
resolving of value ranges (yellow fields) via config key
”.
Project with value ranges, which need to be resolved via Reverse Search
These are catalogs with very complex value ranges, where resolving would create millions and billions of combination possibilities, which exceeds the config limit (max. 25.000 per project, max. 50.000 per catalog) for the inclusion into the full-text index (Lucene index).
When executing the resolve check for these projects a mapping file will be automatically created by which these projects can be found.
The key VARSEARCHRESOLVEORDERNO[4] has to be set correctly what is automatically done when using the plugin Resolve check (Section 5.8.2.1.15.18, “Reverse search ‒ Resolve check (automatic) ”).
These
projects need to have a special mapping file (graphlookup.map
), which
can automatically be created. On this see Section 5.8.2.1.15.18, “Reverse search ‒
Resolve check (automatic) ”.[5]
In special
cases if for certain projects automatic creation is not possible, a
so called ReverseConfig file (pnoreverse.cfg
) can be
manually created. To simplify the process a plugin can be used. See
Section 5.8.2.1.15.21, “
Reverse TypeCode Rule Editor
”.
Special case at 2) and 3): Only a certain number of the actual combination possibilities resulting from value range fields has an order number and is really available or orderable.
-> A CSV
(pnomapping.csv
)
with mapping
information on Order number and
Typecode is stored in the catalog root
directory.
-> Search entry is order number in search mode Search for order number / type code , in fact, the search is performed with the type code in background.
[3] The
Class variables CNSORDERNO
and
CNSTYPECODE
are mapped to the desired variable under Variable with order number and
Variable with type
code. Also see Section 5.13.4, “Simple
assigning of important variables to CNS classification ”.
[4] Key
VARSEARCHRESOLVEORDERNO
.
On project level it is in the project file, on catalog level in
$CADENAS_DATA/23d-libs/<catalogname>/dir.prj
.
No corresponding GUI. Manual intervention not necessary.
[5] Always take care to have an up-to-date full-text search index and/or geo search index for the required catalogs, in order to really have all functions of your software version available. (With V11 SP10 for example, the function Reverse Search – Test reverse search has been added which will access the full-text search index.)