wildcards and coding possibilities

mjkayali

Hi,

In classifications i usually use * or ? or ??.?? to select elements with any value or with certain characters.
what are the other coding possibilities?
is it possible to use something like
!=x
x >= ?
x > 10
it would be nice to have a cheatlist for all the possibilities.

JSN

@mjkayali

You are talking about wildcards, your title is imho a bit missleading.
Anyhow, if the data type allows numeric restrictions then you can work e.g. with operators.

Still, you are right it would be good to have a documentation or a cheatsheet where you can look *. ?, ???, … up.

mjkayali

@JSN
Thank you for showing this example, you’r right I have changed the title little bit and the question as well.
I ment also the coding, it would be nice if you can go further than only (*) and (?) like using (!=) for not equal or searching a non case sensetive string…
*Maybe adding scripting column considering the left column an input and the right one an output can be an idea for future versions of Solibri. but that a bit too far i guess.
for now a cheat sheet with some examples would be good enough.

Sebastiaan

All wildcard can be found here:

https://www.solibri.com/news/release-highlights-enhanced-ito?utm_campaign=In-product ad&utm_source=in-product-ad&utm_medium=in-product-ad&utm_term=9-12-4&utm_content=enhanced-ito

Scroll down to “Other improvements”

JSN

@sebastiaan said in wildcards and coding possibilities:

All wildcard can be found here:
Scroll down to “Other improvements”

You mean this sentence?

We have amended the usage of wildcard characters (* and ?) functionality to also support the use of backslash (* and ?). When using the backslash, users can search for values that include * or ? character, instead of them being recognized as wildcards.

Yes, basically it is * and ? as already mentioned.

@mjkayali Regarding the suggested coding possibilities I guess the Custom Information API might be a workaround atm, however I think you can also achieve a lot with nested classifications if necessary. Although what would be an intended purpose for !x aka a Not Operator which can’t be done with via First/Best matching classification?