Skip to main content

I configured Context Fields that are mapped to calculations associated to a value-based search . 

Once I search, then select results to create context items and map my calculations, I can see the fields in a Context Hub view.

The Context fields I created get mapped to calculations that represent peak temperatures in the range of 1200 to 1400 ‘F. On the Context Hub view, I see results for my context fields with 3 or more decimal places and that is unnecessary. How can I format the values tied to the context fields / value-based search calculations to use 0 decimal places?

 

Hi Yves,

 

Unfortunately, TrendMiner doesn’t currently offer a setting to control the number of decimal places for context fields. The decimal places you’re seeing in ContextHub are the result of TrendMiner’s fixed numeric display rules.

Here’s what’s going on:

  1. ContextHub precision limit

    • TrendMiner stores and displays numeric context field values with up to 15 significant digits.

    • This is hard-coded and not something you can change in the UI or user preferences.

  2. Display formatting rules

    • For values between 1 and 0.001, TrendMiner will always display three decimal places, even if the extra precision is unnecessary.

    • For values ≥ 1e6 or < 0.001, it switches to scientific notation.

    • For values ≥ 1 but < 1e6, you’ll see decimal notation, and depending on the exact value, TrendMiner may still display multiple decimal places to preserve significant digits.

    So when your peak temperatures are around 1200–1400 °F, TrendMiner applies its standard decimal display rule and keeps 3+ decimal places.

If you want you can always suggest a product idea, so we can further improve TrendMiner for you!

 

Kind regards

Frederik Vandael


Thanks ​@yracette for creating a feature idea. For future reference, I will link it here: 

 


Reply