Chapter 16. V11.00 SP4
16.2. Restriction of resolving value ranges (yellow fields)
Prev  Next

16.2. Restriction of resolving value ranges (yellow fields)

The possible combinations resulting from resolving of yellow fields can be huge and extremely increase the index. That's why the allowed number of variants per catalog and per project is restricted by configuration file.[64]

Furthermore, in PARTproject, it can be set, whether order numbers shall be indexed depending on value ranges.

Restriction of resolving of yellow fields

The maximum number of allowed possible combinations, which result from values of value range variables (yellow fields), can be restricted in the configuration file partsol.cfg. The setting applies for all catalogs.

partsol.cfg

  • MaxProjectResolveRange means, the stated number of variants must not be exceeded per project by the resolving of value ranges.

    MaxProjectResolveRange=25000 (default)

  • MaxCatalogResolveRange means, the stated number of variants must not be exceeded per catalog by the resolving of value ranges.

    MaxCatalogResolveRange=50000 (default)

If one of these limits is exceeded, then no variants are indexed for the whole catalog.

Indexing order numbers depending on value ranges: Setting options catalog and project specific

In PARTproject -> Edit project -> tabbed page General -> Search index creation -> Index order numbers dependent on value ranges, specific settings for single catalogs or projects can be performed, if order numbers shall be indexed depending on value ranges.

Setting options on catalog level:

Value range:

  • Yes:

    VARSEARCHRESOLVEORDERNO=1

  • No: (default)

    VARSEARCHRESOLVEORDERNO=0

    or key VARSEARCHRESOLVEORDERNO is not available

    [Note]Note

    Since the feature is new[a], the default setting "No" still might be used in most catalogs. (Then on project level the default setting "Use catalog setting" is used.)

    [a] April 2018

On catalog level, the key VARSEARCHRESOLVEORDERNO is in $CADENAS_DATA/23d-libs/<catalogname>/dir.prj.

Setting options on project level:

The catalog setting can be overwritten per project. Unless Use catalog setting is set, then the catalog setting is used. And this is the default.

  • Yes:

    VARSEARCHRESOLVEORDERNO=1

  • No:

    VARSEARCHRESOLVEORDERNO=0

  • Use catalog setting: (default)

    ("Catalog setting" is the setting on the catalog's root node.)

    Key VARSEARCHRESOLVEORDERNO not available

On project level the key VARSEARCHRESOLVEORDERNO is in the project file.

[Tip]Tip

A modeller can act in this way: First he sets if indexing should be done or not. If there are many projects to be indexed in the catalog, then he sets "Yes". If there are few, then "No".

Then he goes to those projects, which differ from the catalog's standard and there, makes the setting. This saves effort.

Resolving value range fields by scripting

As of V11 SP4 there is a new search method Search for order number or type name in addition.

At first this function searches for order number or type code via Lucene index. If nothing is found in this way, then a reverse search via script is executed. So a script for reverse search has to be created for a catalog, if the limits (see above) have been exceeded. If there are no value ranges in a catalog at all, then there is no need to create a script for reverse search.

Example project with many value range variables, which interactively build up the part number

Example project with many value range variables, which interactively build up the part number



[64] #90015

Prev Up Next
16.1. Resolving value ranges: Testing ReverseScripts Home 16.3.  Authentication